Triple
T35416998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Traiectum ad Mosam |
E1023669
|
entity |
| Predicate | provinceOfEmpire |
P197213
|
FINISHED |
| Object | Germania Inferior |
—
|
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: Germania Inferior | Statement: [Traiectum ad Mosam, provinceOfEmpire, Germania Inferior]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: provinceOfEmpire Context triple: [Traiectum ad Mosam, provinceOfEmpire, Germania Inferior]
-
A.
governingEmpire
Indicates that one entity serves as the ruling imperial power that controls or governs another entity.
-
B.
foundedInEmpire
Indicates that an entity (such as an organization, city, or institution) was established during the existence or rule of a specified empire.
-
C.
administrativeCenterForEmpire
Indicates that a location served as the main administrative center or capital for a particular empire.
-
D.
originatingEmpire
Indicates the empire from which an entity, such as a person, object, or event, originally comes or was first established.
-
E.
regionOfDynasty
Indicates the geographic region or area in which a given dynasty held power or was primarily based.
- 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_69f76df54bac8190bd0d3b0eb35cda5f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe7bfc94bc81909eeec946e8c1c450 |
completed | May 9, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69fe7b74a1188190886f128e07f712da |
completed | May 9, 2026, 12:10 a.m. |
| PDg | Predicate description generation | batch_69fe7bfb71b08190bed5c33e4ab7afff |
completed | May 9, 2026, 12:12 a.m. |
Created at: May 3, 2026, 4:03 p.m.