Triple
T29616465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chosen One prophecy |
E754876
|
entity |
| Predicate | candidateIdentifiedAs |
P167510
|
FINISHED |
| Object | Anakin Skywalker |
—
|
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: Anakin Skywalker | Statement: [Chosen One prophecy, candidateIdentifiedAs, Anakin Skywalker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: candidateIdentifiedAs Context triple: [Chosen One prophecy, candidateIdentifiedAs, Anakin Skywalker]
-
A.
candidateFor
Indicates that one entity is being considered or proposed as a possible choice, option, or selection for another entity (such as a role, position, or outcome).
-
B.
candidateType
Indicates the classification or category assigned to a candidate within a given context or process.
-
C.
identifiedIn
Indicates that an entity is recognized, discovered, or documented within a specified source, context, or location.
-
D.
recognizedAsRepresentativeBy
Indicates that one entity is acknowledged or accepted by another entity as acting as its representative.
-
E.
candidateVettingBy
Indicates that a candidate is being evaluated, screened, or vetted by a specified person, group, or process.
- 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_69f0ef85f62081909842b59fdf8717e1 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f66e2198f88190b384af5844ab9415 |
completed | May 2, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 28, 2026, 6:31 p.m.