Triple
T28867879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | L’ultimo uomo della Terra |
E729051
|
entity |
| Predicate | followedByAdaptation |
P183994
|
FINISHED |
| Object | The Omega Man |
—
|
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: The Omega Man | Statement: [L’ultimo uomo della Terra, followedByAdaptation, The Omega Man]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followedByAdaptation Context triple: [L’ultimo uomo della Terra, followedByAdaptation, The Omega Man]
-
A.
precededByAdaptation
Indicates that one entity occurs only after a prior adaptation process has taken place.
-
B.
followedByInProtocol
Indicates that one step, action, or event in a protocol occurs immediately after another as the next prescribed step.
-
C.
followedByInSequence
Indicates that one event or element directly succeeds another in an ordered sequence.
-
D.
followedByComponent
Indicates that one component directly succeeds another component in a defined sequence or order.
-
E.
followedByClass
Indicates that one class or type is immediately succeeded by another class or type in a defined sequence or ordering.
- 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_69f031a01cbc8190ba87270bb6fe4639 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f7aaabb58c8190bf81673608ecfb6e |
completed | May 3, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f7aa6795f481908940838ee7041ff5 |
completed | May 3, 2026, 8:04 p.m. |
Created at: April 28, 2026, 6:49 a.m.