Triple
T14240419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akhtar |
E352987
|
entity |
| Predicate | laterAppearanceIn |
P41450
|
FINISHED |
| Object | film adaptation The History Boys (2006) |
—
|
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: film adaptation The History Boys (2006) | Statement: [Akhtar, laterAppearanceIn, film adaptation The History Boys (2006)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterAppearanceIn Context triple: [Akhtar, laterAppearanceIn, film adaptation The History Boys (2006)]
-
A.
laterAppearanceName
Indicates that an entity is known by a different name in a later appearance or time period.
-
B.
laterIn
Indicates that one event, state, or time point occurs after another in temporal order.
-
C.
laterAppearancesIn
chosen
Indicates that one entity makes additional or subsequent appearances in relation to another entity after an initial occurrence.
-
D.
reappearsAt
Indicates that an entity, after having disappeared or been absent, becomes present again at a specific location or point in time.
-
E.
reappearsIn
Indicates that an entity that previously appeared becomes present or visible again in the same or another context.
- 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_69d8278adc7c8190a9218d69bce3c4e6 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de62432fb48190b153805b85c4f2d2 |
completed | April 14, 2026, 3:50 p.m. |
| PD | Predicate disambiguation | batch_69de05bf069c8190b69f00f00f5eb126 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:08 a.m.