Triple
T27062614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Rocky Tract |
E685084
|
entity |
| Predicate | laterGoverningPower |
P30069
|
FINISHED |
| Object | Roman Empire |
—
|
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: Roman Empire | Statement: [The Rocky Tract, laterGoverningPower, Roman Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterGoverningPower Context triple: [The Rocky Tract, laterGoverningPower, Roman Empire]
-
A.
laterGovernedAs
Indicates that an entity subsequently held governing authority over another entity at a later time.
-
B.
laterGoverningSystem
Indicates that one governing system succeeds and replaces another at a later point in time.
-
C.
laterPoliticalSystemUnderRule
Indicates that one political system came under the rule or authority of another political system at a later point in time.
-
D.
governingPowerRelationship
Indicates a relationship where one entity holds authoritative control, influence, or ruling power over another entity.
-
E.
governingBodyAfter
chosen
Indicates that one governing body succeeds another as the official authority over the same entity or jurisdiction.
- 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_69ef14835fcc81908bd737b4267ae528 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: April 27, 2026, 8:22 a.m.