Triple
T6179951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belgae |
E137915
|
entity |
| Predicate | urbanCenters |
P44289
|
FINISHED |
| Object | oppida |
—
|
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: oppida | Statement: [Belgae, urbanCenters, oppida]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: urbanCenters Context triple: [Belgae, urbanCenters, oppida]
-
A.
notableCityCenter
Indicates that a location serves as a prominent or significant central area within a city.
-
B.
majorUrbanCenterIn
Indicates that a city or metropolitan area functions as a primary or significant urban center within the specified region or administrative unit.
-
C.
capitalOrMajorCenter
Indicates that a location serves as a capital city or a primary major center (political, economic, or cultural hub) for a larger region or entity.
-
D.
isUrbanCenter
chosen
Indicates that a place functions as a primary, densely developed hub of population, services, and activities within a region.
-
E.
isUrbanCentreFor
Indicates that one place functions as the primary urban hub or central city serving another area or population.
- 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_69c008a80f748190ba3d07ffc81acb29 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05dcb77948190b5385438f81bf0a8 |
completed | March 22, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69c055fa0a808190bda37832e3ac150c |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:18 p.m.