Triple
T32552514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The One |
E832011
|
entity |
| Predicate | firstKnownIncarnation |
P185246
|
FINISHED |
| Object | Neo |
E195723
|
NE 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: Neo | Statement: [The One, firstKnownIncarnation, Neo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstKnownIncarnation Context triple: [The One, firstKnownIncarnation, Neo]
-
A.
incarnationOf
Indicates that one entity is a concrete embodiment, manifestation, or earthly form of another, typically more abstract or divine, entity.
-
B.
earlierIncarnationOf
chosen
Indicates that one entity is a previous incarnation or earlier life-form of another entity in a sequence of reincarnations or transformations.
-
C.
founderInFirstIncarnation
Indicates that the subject entity was the original founder of the object entity in its first established form or incarnation.
-
D.
firstAppearsOnEarth
Indicates that the referenced entity makes its earliest known appearance or occurrence on Earth at the specified time or context.
-
E.
introducesIncarnation
Indicates that one entity brings about, initiates, or presents the embodiment or incarnation of another entity in a concrete or manifest form.
- F. None of above.
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_69f34926b9848190ace47d2dd0a0de7c |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a347b8c5ec081909b55407fd3974089 |
completed | June 18, 2026, 11:13 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:02 a.m.