Triple
T20385452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | It Had to Be You |
E497945
|
entity |
| Predicate | hasAlternateKey |
P139918
|
FINISHED |
| Object | E-flat major |
—
|
LITERAL 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: E-flat major | Statement: [It Had to Be You, hasAlternateKey, E-flat major]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlternateKey Context triple: [It Had to Be You, hasAlternateKey, E-flat major]
-
A.
hasAlternateMemberType
Indicates that an entity is associated with a different or substitute type of member than its primary or standard member type.
-
B.
hasAlternativeReferent
Indicates that an entity can also be referred to or identified by an alternative name, label, or reference.
-
C.
hasAlternateCut
Indicates that an entity has an alternative edited version or cut, distinct from its primary or original form.
-
D.
hasAlternativeElements
Indicates that one entity includes or is associated with elements that can serve as substitutes or options in place of other elements.
-
E.
hasAlternateRegisterSet
Indicates that an entity is associated with an additional, distinct set of registers that can be used as an alternative to its primary register set.
- F. None of above. chosen
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_69e0b4a71ebc8190b153a36c738730f4 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6790a31a4819099b2e6df2bafe547 |
completed | April 20, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69e57648be3c81908256838228cabf5c |
completed | April 20, 2026, 12:41 a.m. |
| PDg | Predicate description generation | batch_69e58d7481508190a87c8b88f9df9879 |
completed | April 20, 2026, 2:20 a.m. |
Created at: April 16, 2026, 11:28 a.m.