Triple
T18206689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World State caste system |
E435919
|
entity |
| Predicate | hasTopCaste |
P16727
|
FINISHED |
| Object | Alpha |
—
|
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: Alpha | Statement: [World State caste system, hasTopCaste, Alpha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTopCaste Context triple: [World State caste system, hasTopCaste, Alpha]
-
A.
hasCast
Indicates that a creative work features a particular group of performers or actors.
-
B.
hasTopness
Indicates that an entity possesses the quantum property of topness, typically associated with the presence or contribution of a top quark.
-
C.
hasCaste
chosen
Indicates that an entity belongs to or is associated with a particular caste within a social or hierarchical system.
-
D.
hasEnsembleCast
Indicates that a work features an ensemble cast, meaning multiple principal performers share roughly equal prominence rather than having a single clear lead.
-
E.
hasNotableCrewMember
Indicates that an entity is associated with a crew member who is considered notable or distinguished in some way.
- 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_69d8b90dba6481908e119eb9aa4ca0cb |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4e2243de081908a5bcc7e2072eae7 |
completed | April 19, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_69e4332155d88190b106d0dceb4554af |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:32 a.m.