Triple
T28205388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | You Will Be My Son |
E717002
|
entity |
| Predicate | hasEnglishReleaseTitle |
P114637
|
FINISHED |
| Object | You Will Be My Son |
—
|
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 Will Be My Son | Statement: [You Will Be My Son, hasEnglishReleaseTitle, You Will Be My Son]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEnglishReleaseTitle Context triple: [You Will Be My Son, hasEnglishReleaseTitle, You Will Be My Son]
-
A.
hasApproximateEnglishTitle
Indicates that an entity is associated with an English title that is an approximate or non-exact rendering of its original title.
-
B.
hasTitleInEnglishOrthography
chosen
Indicates that an entity has a specific title expressed using English spelling and writing conventions.
-
C.
hasEnglishEdition
Indicates that one entity has a version or edition of itself that is produced or available in the English language.
-
D.
hasEnglishName
Indicates that an entity is associated with a name expressed in the English language.
-
E.
hasTitleInModernEnglish
Indicates that an entity is associated with a specific title expressed in modern English.
- 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_69efd6b826908190857e6e7dad74ed93 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d26ceb08819091c71c001e954936 |
completed | May 3, 2026, 4:43 a.m. |
Created at: April 27, 2026, 10:35 p.m.