Triple
T25313368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lingones |
E634664
|
entity |
| Predicate | territoryFeature |
P159101
|
FINISHED |
| Object | upper Seine basin |
—
|
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: upper Seine basin | Statement: [Lingones, territoryFeature, upper Seine basin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: territoryFeature Context triple: [Lingones, territoryFeature, upper Seine basin]
-
A.
territoryFeature
chosen
Indicates that a specific geographic or physical feature is located within, characterizes, or is part of a given territory.
-
B.
territoryType
Indicates the specific kind or classification of a territory associated with an entity (e.g., country, region, zone, or jurisdiction type).
-
C.
politicalFeature
Indicates that an entity possesses a political characteristic, attribute, or aspect relevant to governance, power structures, or public policy.
-
D.
governedTerritoryCharacteristic
Indicates that a governing entity is associated with a specific characteristic or attribute of the territory it governs.
-
E.
partOfTerritory
Indicates that one geographic or administrative area is contained within, and forms a constituent portion of, another territory.
- 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_69e75a9847c08190bb02990d06d5ffb7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f55e519978819087a1676564a74630 |
completed | May 2, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69f4a0edd10c81908a052ab864d57c54 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 21, 2026, 1:27 p.m.