Triple
T8312087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Londinium |
E194612
|
entity |
| Predicate | wasGovernedBy |
P76127
|
FINISHED |
| Object | Roman provincial 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: Roman provincial administration | Statement: [Londinium, wasGovernedBy, Roman provincial administration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasGovernedBy Context triple: [Londinium, wasGovernedBy, Roman provincial administration]
-
A.
governedByInPast
chosen
Indicates that an entity was under the rule, control, or authority of another entity during a previous time period.
-
B.
governedByAtTimeOfEvent
Indicates that an entity is under the authority or control of a particular governing agent specifically at the time a given event occurs.
-
C.
governingSince
Indicates that one entity has held a governing or ruling role over another entity starting from a specified point in time.
-
D.
laterGovernedAs
Indicates that an entity subsequently held governing authority over another entity at a later time.
-
E.
hadPrincipalLeader
Indicates that an entity was led or headed by a primary or chief leader.
- 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_69ca82e6e2648190a31eaf6f4f757b2a |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7f504ca8819087fb1f731f7a7cfd |
completed | March 31, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69cb70bb3a708190bc705222092da614 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:54 p.m.