Triple
T38587769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Military Ward |
E932382
|
entity |
| Predicate | inUniverseGovernment |
P193093
|
FINISHED |
| Object | Council of Three Hammers |
—
|
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: Council of Three Hammers | Statement: [Military Ward, inUniverseGovernment, Council of Three Hammers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inUniverseGovernment Context triple: [Military Ward, inUniverseGovernment, Council of Three Hammers]
-
A.
inUniverseGovernmentForm
Indicates that an entity has a specific form or type of government within a fictional or defined universe.
-
B.
inUniverseGoverningBody
chosen
Indicates that a governing body exists and operates within the context or setting of a particular fictional or defined universe.
-
C.
inUniverse
Indicates that one entity exists, occurs, or is set within the fictional or conceptual universe defined by another entity.
-
D.
inUniverseAuthority
Indicates that one entity holds authoritative power or governing control over another within a specific fictional or defined universe or setting.
-
E.
inGovernmentFrom
Indicates that an entity holds or has held a government position or role starting from a specified point in time.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd974d75e08190af46b1d608769f3b |
completed | May 8, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69fd94ff792c8190bedf4a639d3da809 |
completed | May 8, 2026, 7:47 a.m. |
Created at: May 3, 2026, 4:32 p.m.