Triple
T31104947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bene Tleilax |
E792768
|
entity |
| Predicate | subordinateClass |
P170086
|
FINISHED |
| Object | Face Dancers |
—
|
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: Face Dancers | Statement: [Bene Tleilax, subordinateClass, Face Dancers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subordinateClass Context triple: [Bene Tleilax, subordinateClass, Face Dancers]
-
A.
subordinateClasses
chosen
Indicates that certain classes are hierarchically below or dependent on another class within an organizational or classification structure.
-
B.
subclassOf
Indicates that one class is a more specific type of another class, inheriting its characteristics as a subset of it.
-
C.
subordinateTo
Indicates that one entity holds a lower rank, status, or authority and is subject to the control, direction, or oversight of another entity.
-
D.
classBelow
Indicates that one class is positioned lower than another in a hierarchy, ordering, or structural arrangement.
-
E.
subbranchOf
Indicates that one entity is a subordinate or secondary branch derived from, and structurally dependent on, 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_69f224cfd5d881908ec6447bc321cd58 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c234d648190a243fb2b107136a9 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:03 p.m.