Triple
T35648010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Praetor Shinzon |
E1030060
|
entity |
| Predicate | governmentOver |
P194118
|
FINISHED |
| Object | Romulan Star Empire |
E315772
|
NE 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: Romulan Star Empire | Statement: [Praetor Shinzon, governmentOver, Romulan Star Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governmentOver Context triple: [Praetor Shinzon, governmentOver, Romulan Star Empire]
-
A.
government1
Indicates that one entity functions as the governing authority or administration over another entity.
-
B.
government2
chosen
Indicates a relationship where an entity serves as or functions as the governing authority or administrative body over another entity.
-
C.
government3
Indicates a relationship where an entity functions as or is associated with a government or governing body in a given context.
-
D.
governmentOutcome
Indicates the result, consequence, or effect produced by a government’s decisions, actions, or policies.
-
E.
governmentalCore
Indicates that something serves as a central, essential, or foundational part of a government or governmental system.
- F. None of above.
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_69f76e0938088190a8f199631e97dec3 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a01e27bb77c8190a7686b77a524f177 |
completed | May 11, 2026, 2:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3a380342b0819099f5e8697c9d5cbd |
completed | June 23, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_6a01da2614788190b31db15539f5ba58 |
completed | May 11, 2026, 1:31 p.m. |
Created at: May 3, 2026, 4:05 p.m.