Triple
T18370715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vorta |
E446173
|
entity |
| Predicate | primaryRoleInDominion |
P130860
|
FINISHED |
| Object | administration |
—
|
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: administration | Statement: [Vorta, primaryRoleInDominion, administration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryRoleInDominion Context triple: [Vorta, primaryRoleInDominion, administration]
-
A.
deFactoRole
Indicates that an entity effectively functions in a role or capacity in practice, even if that role is not formally or officially assigned.
-
B.
roleInGameplay
Indicates the specific function or responsibility an entity has within the context of gameplay or game mechanics.
-
C.
roleInDomino
Indicates that an entity participates in a domino effect or chain of events by occupying a specific role or position within that causal sequence.
-
D.
questRole
Indicates the specific function or part an entity plays within a quest or mission.
-
E.
roleInDUNE
Indicates that an entity has a specific acting role or participation in the production of the film "Dune."
- 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_69d8b9f370b88190b1e5081c2c238e7f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e5175324e48190a00572e15423feb7 |
completed | April 19, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69e44fed3fdc81908f4ed6a81db42416 |
completed | April 19, 2026, 3:45 a.m. |
| PDg | Predicate description generation | batch_69e451a1bda48190a9cd1db436d4be62 |
completed | April 19, 2026, 3:53 a.m. |
Created at: April 10, 2026, 10:44 a.m.