Triple
T5873817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Germania Inferior |
E130579
|
entity |
| Predicate | provinceType |
P67341
|
FINISHED |
| Object | imperial province |
—
|
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: imperial province | Statement: [Germania Inferior, provinceType, imperial province]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: provinceType Context triple: [Germania Inferior, provinceType, imperial province]
-
A.
provinceName
Indicates that a province entity is associated with its specific name as a textual label.
-
B.
teamProvinceOrState
Indicates that a team is located in, or associated with, a particular province or state.
-
C.
primaryStates
Indicates that certain states or conditions are the main or most fundamental ones within a given context or system.
-
D.
stateOrTerritory
Indicates that one entity is a state or territory that is politically or administratively associated with another entity.
-
E.
isProvinceOf
Indicates that one region holds the administrative status of a province within, and is governed as a subnational division of, another political entity.
- 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_69c0085523688190bfd487479ce819e6 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0432fea5881909f5c291dd8db6105 |
completed | March 22, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69c033499ca08190bd26cee5b03f6306 |
completed | March 22, 2026, 6:22 p.m. |
| PDg | Predicate description generation | batch_69c0432f06fc8190bc047d52ffc30d59 |
completed | March 22, 2026, 7:29 p.m. |
Created at: March 22, 2026, 3:57 p.m.