Triple
T30401872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Chosen One |
E773369
|
entity |
| Predicate | prophecyConcern |
P146338
|
FINISHED |
| Object | destruction of the Sith |
—
|
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: destruction of the Sith | Statement: [The Chosen One, prophecyConcern, destruction of the Sith]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prophecyConcern Context triple: [The Chosen One, prophecyConcern, destruction of the Sith]
-
A.
prophecyMade
Indicates that a prophetic statement or prediction has been declared by one entity concerning a future event or outcome involving another entity.
-
B.
subjectOfProphecy
Indicates that the subject is foretold or predicted to play a significant role or experience a specific event according to a prophecy.
-
C.
prophecyContent
chosen
Indicates that the object expresses the specific message, information, or details contained within a prophecy.
-
D.
prophecyHeardBy
Indicates that a prophecy was heard or received by a particular entity.
-
E.
prophecySource
Indicates that one entity is the origin or provider of a particular prophecy concerning another entity or event.
- 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_69f2248facd48190b183c3f3ca6daef7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68a16debc8190a12f5f65ced055d7 |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:03 p.m.