Triple
T29103298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bagacum Nerviorum |
E736694
|
entity |
| Predicate | wasPrincipalSettlementOf |
P13187
|
FINISHED |
| Object | Nervii |
—
|
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: Nervii | Statement: [Bagacum Nerviorum, wasPrincipalSettlementOf, Nervii]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasPrincipalSettlementOf Context triple: [Bagacum Nerviorum, wasPrincipalSettlementOf, Nervii]
-
A.
foundedAsSettlementFor
Indicates that one entity was originally established specifically to serve as a settlement for another entity (such as a group, population, or community).
-
B.
originOfSettlement
Indicates the place, source, or starting point from which a settlement was established or originated.
-
C.
formerMainSettlement
Indicates that a location was previously the primary or most important settlement of a given area, but no longer holds that status.
-
D.
mainSettlement
chosen
Indicates that one settlement serves as the primary or most important settlement associated with a given area, region, or administrative unit.
-
E.
hasHumanSettlement
Indicates that a location or area contains or is the site of a human settlement, such as a town, village, or city.
- 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_69f077ec765c81909474c88bcc8bab43 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f661b730a08190ab462338202694b4 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 11:13 a.m.