Triple
T23524978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gauls |
E574607
|
entity |
| Predicate | subsequentProvince |
P123680
|
FINISHED |
| Object | Gallia Narbonensis |
—
|
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: Gallia Narbonensis | Statement: [Gauls, subsequentProvince, Gallia Narbonensis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subsequentProvince Context triple: [Gauls, subsequentProvince, Gallia Narbonensis]
-
A.
laterProvince
Indicates that one administrative region or province succeeds another in time, coming into existence or effect after the other.
-
B.
successorProvinceOrState
chosen
Indicates that one province or state has officially replaced or continued the role of another as its successor.
-
C.
laterProvinceName
Indicates that an entity (such as a region or administrative unit) is known by a different province name at a later point in time.
-
D.
previousProvince
Indicates that one province was the immediately preceding administrative region of another in a temporal or historical sequence.
-
E.
formerProvince
Indicates that an entity was previously a province of another entity but no longer holds that administrative status.
- 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_69e245bb3dcc8190ba9a2b35972b58d0 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1ac72bfb88190b7da3837e66e851c |
completed | April 29, 2026, 7 a.m. |
| PD | Predicate disambiguation | batch_69f1189d75b48190a1c01928a993c9fb |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:09 p.m.