Triple
T8313095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belgica Prima |
E194637
|
entity |
| Predicate | correspondsToModernRegion |
P36806
|
FINISHED |
| Object | parts of modern Luxembourg |
—
|
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: parts of modern Luxembourg | Statement: [Belgica Prima, correspondsToModernRegion, parts of modern Luxembourg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: correspondsToModernRegion Context triple: [Belgica Prima, correspondsToModernRegion, parts of modern Luxembourg]
-
A.
historicalRegionCorrespondsTo
chosen
Indicates that a historical region matches or aligns with a specific region, territory, or administrative unit in terms of location, extent, or identity.
-
B.
modernRegion
Indicates that an entity is located within or associated with a contemporary, present-day geographic or administrative region.
-
C.
historicalRegionNowInCountry
Indicates that a historical region is currently located within the borders or jurisdiction of a specified modern country.
-
D.
locatedInModernAdministrativeRegion
Indicates that an entity is geographically situated within the boundaries of a current, officially recognized administrative region.
-
E.
historicalRegionCode
Indicates that an entity is associated with a specific code identifying a historical region.
- 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_69ca82e6e2648190a31eaf6f4f757b2a |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7f5173c881909f2e84d53ea33a98 |
completed | March 31, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69cb70bb3a708190bc705222092da614 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:54 p.m.