Triple
T35418067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maria (You Were the Only One) |
E1023698
|
entity |
| Predicate | isPartOfSingle |
P45544
|
FINISHED |
| Object | Got to Be There |
E312869
|
NE FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Got to Be There | Statement: [Maria (You Were the Only One), isPartOfSingle, Got to Be There]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfSingle Context triple: [Maria (You Were the Only One), isPartOfSingle, Got to Be There]
-
A.
partOfSingle
chosen
Indicates that one entity is a component or member of exactly one specific whole or collection, and not shared among multiple such wholes.
-
B.
isSingle
Indicates that an entity is not currently in a romantic relationship or legally married.
-
C.
isOnlyPartOf
Indicates that an entity is a component exclusively of a specific whole and not of any other whole.
-
D.
isSoloPartFor
Indicates that something functions as an individual or standalone component within a larger whole or composition.
-
E.
isPartially
Indicates that one entity is included within another to some extent, but not completely or fully.
- F. None of above.
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f76df54bac8190bd0d3b0eb35cda5f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff9a25407c81909faa86e72a7a9d17 |
completed | May 9, 2026, 8:33 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3840265b4081909d0cb289f29c619e |
completed | June 21, 2026, 7:48 p.m. |
| PD | Predicate disambiguation | batch_69ff99c613688190a03b2f93d5ccad2b |
completed | May 9, 2026, 8:32 p.m. |
Created at: May 3, 2026, 4:03 p.m.