Triple
T26876376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baby (You’ve Got What It Takes) |
E676760
|
entity |
| Predicate | hasEarlierTitleVariant |
P160063
|
FINISHED |
| Object | You’ve Got What It Takes |
—
|
NE NERFINISHED |
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: You’ve Got What It Takes | Statement: [Baby (You’ve Got What It Takes), hasEarlierTitleVariant, You’ve Got What It Takes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEarlierTitleVariant Context triple: [Baby (You’ve Got What It Takes), hasEarlierTitleVariant, You’ve Got What It Takes]
-
A.
hasFormerTitle
Indicates that an entity previously held a specific title or position but no longer does.
-
B.
hasLaterTitle
Indicates that one title occurs chronologically after another title in a sequence or timeline.
-
C.
haveAlternativeTitle
Indicates that an entity is known by one or more alternative titles or names in addition to its primary title.
-
D.
hasWorkTitleVariant
chosen
Indicates that an entity has an alternative or variant form of its work title, such as a different wording, spelling, or language version of the same title.
-
E.
hasShorterSingleVersionTitle
Indicates that one entity’s title is a shorter, single-version form of another entity’s title.
- F. None of above.
Provenance (3 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_69eee9bb44988190b6e11652d028bc59 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f6247480cc8190a887eedaeb94615c |
completed | May 2, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69f623a7539c8190b71797f583da9f63 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 5:36 a.m.