Triple
T35843575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Zod |
E1036150
|
entity |
| Predicate | planetaryRole |
P183881
|
FINISHED |
| Object | military dynasty |
—
|
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: military dynasty | Statement: [House of Zod, planetaryRole, military dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: planetaryRole Context triple: [House of Zod, planetaryRole, military dynasty]
-
A.
notablePlanetRole
Indicates that a planet holds a significant or distinguished role or function within a particular context or system.
-
B.
roleAtThePlanet
Indicates that an entity holds or performs a specific role or function at, on, or for a particular planet.
-
C.
roleInGalaxy
Indicates the specific function, status, or influence an entity holds within the broader structure or dynamics of a galaxy.
-
D.
roleAtPluto
Indicates that an entity holds or held a specific role or position within the organization or project named Pluto.
-
E.
planetaryProtectionRole
Indicates the specific responsibility or function an entity has in planning, implementing, or overseeing measures to prevent biological contamination between Earth and other celestial bodies.
- 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_69f76e1a29e8819088280f26096aeb55 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aaabb58c8190bf81673608ecfb6e |
completed | May 3, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d435288190b30b1991fb003121 |
completed | May 3, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f7aa33e0488190a135166bb67e1118 |
completed | May 3, 2026, 8:04 p.m. |
Created at: May 3, 2026, 4:06 p.m.