Triple
T5190183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terence Young |
E117132
|
entity |
| Predicate | predecessorInSeries |
P97
|
FINISHED |
| Object | none (first James Bond film director) |
—
|
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: none (first James Bond film director) | Statement: [Terence Young, predecessorInSeries, none (first James Bond film director)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorInSeries Context triple: [Terence Young, predecessorInSeries, none (first James Bond film director)]
-
A.
predecessorSeries
Indicates that one series directly precedes another in an ordered sequence or lineage.
-
B.
predecessorControl
Indicates that one entity has control or authority over another entity that precedes it in a sequence, process, or hierarchy.
-
C.
predecessor
chosen
Indicates that one entity comes before another in an ordered sequence or succession.
-
D.
predecessorProject
Indicates that one project temporally or logically comes before and leads into another project in a sequence or dependency chain.
-
E.
predecessorState
Indicates that one state directly precedes another in a sequence or process.
- 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_69bd44620ff48190bcac01782107a397 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd79ebbfd081909a19b903c227fc1f |
completed | March 20, 2026, 4:46 p.m. |
| PD | Predicate disambiguation | batch_69bd77b7e8b4819092ec3965e11f2dea |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:46 p.m.