Triple
T30401850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Chosen One |
E773369
|
entity |
| Predicate | prophecyLanguage |
P169750
|
FINISHED |
| Object | Jedi prophecy |
—
|
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: Jedi prophecy | Statement: [The Chosen One, prophecyLanguage, Jedi prophecy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prophecyLanguage Context triple: [The Chosen One, prophecyLanguage, Jedi prophecy]
-
A.
prophecySource
Indicates that one entity is the origin or provider of a particular prophecy concerning another entity or event.
-
B.
prophecyTradition
Indicates a relationship where a prophetic message, practice, or belief is transmitted, preserved, or interpreted within a particular religious or cultural tradition.
-
C.
prophecyKnownAs
Indicates that a particular prophecy is referred to or recognized by a specific name or title.
-
D.
prophecyContent
Indicates that the object expresses the specific message, information, or details contained within a prophecy.
-
E.
prophecyMade
Indicates that a prophetic statement or prediction has been declared by one entity concerning a future event or outcome involving another entity.
- 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_69f2248facd48190b183c3f3ca6daef7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68619900c8190b8fcaaeb0c936da9 |
completed | May 2, 2026, 11:17 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
| PDg | Predicate description generation | batch_69f67f7e116c819099aec724e9ef3763 |
completed | May 2, 2026, 10:49 p.m. |
Created at: April 29, 2026, 8:03 p.m.