Triple
T8497717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jedi Order |
E201139
|
entity |
| Predicate | eliteGroup |
P20239
|
FINISHED |
| Object | Jedi Council members |
—
|
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 Council members | Statement: [Jedi Order, eliteGroup, Jedi Council members]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eliteGroup Context triple: [Jedi Order, eliteGroup, Jedi Council members]
-
A.
eliteField
Indicates that the entity is associated with a highly selective or top-tier field, domain, or area of specialization.
-
B.
elite
chosen
Indicates that the subject belongs to a select, superior, or highly privileged subset within a larger group or category.
-
C.
eliteStatusProgram
Indicates a relationship where an entity is enrolled in or associated with a special high-tier or privileged status program.
-
D.
representedGroups
Indicates that an entity serves as an official or recognized representative for one or more groups.
-
E.
typicalGroup
Indicates that the subject belongs to or represents a standard, characteristic, or commonly occurring group associated with the object.
- 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_69ca831ee390819095fae73400bbfafc |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe583aebc819090345684bfa1fca2 |
completed | March 31, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69cbd10a4b0881909e254117780dc823 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:13 p.m.