Triple
T38591127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jedi Consular |
E932454
|
entity |
| Predicate | classMirror |
P119587
|
FINISHED |
| Object | Sith Inquisitor |
—
|
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: Sith Inquisitor | Statement: [Jedi Consular, classMirror, Sith Inquisitor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: classMirror Context triple: [Jedi Consular, classMirror, Sith Inquisitor]
-
A.
mirroredBy
chosen
Indicates that one entity serves as a reflective counterpart or reversed representation of another.
-
B.
mirrorType
Indicates that one entity is a specific kind or category of mirror in relation to another entity.
-
C.
logicalMirrorOf
Indicates that one entity is the logical counterpart or inverse of another, such that their logical structures correspond in a mirrored or dual manner.
-
D.
mirroredOn
Indicates that one entity is a reflective counterpart of another, such that its structure, appearance, or configuration is reversed or symmetrically aligned relative to the other.
-
E.
mirrorsStructureOf
Indicates that one entity’s overall organization, pattern, or arrangement closely corresponds to and reflects the structure of another entity.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd3a69f1e08190a11aed015bff0858 |
completed | May 8, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69fd39124180819080ca7911d3515d6d |
completed | May 8, 2026, 1:14 a.m. |
Created at: May 3, 2026, 4:32 p.m.