Triple
T37257285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lotharingians |
E924164
|
entity |
| Predicate | borderlandRole |
P67824
|
FINISHED |
| Object | frontier between French and German spheres |
—
|
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: frontier between French and German spheres | Statement: [Lotharingians, borderlandRole, frontier between French and German spheres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderlandRole Context triple: [Lotharingians, borderlandRole, frontier between French and German spheres]
-
A.
borderRegionRole
chosen
Indicates a role or function that an entity has specifically in relation to a border region or border area.
-
B.
hasBorderTownRole
Indicates that an entity serves in an official capacity or role specifically related to a town located on or near a border.
-
C.
borderRegion
Indicates a region that lies along or near the boundary separating two distinct geographic or political areas.
-
D.
borderTribe
Indicates that a tribe is located along or adjacent to a border, such as the boundary between regions, states, or countries.
-
E.
borderCountrySide
Indicates that one country shares a land border with the side or region of another country.
- 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_69f76eabd6c481909d414a80a1345c98 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a00037bf4148190a58593d30efdd3f8 |
completed | May 10, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_6a0000b7af608190b718fc4111bcdad8 |
completed | May 10, 2026, 3:51 a.m. |
Created at: May 3, 2026, 4:15 p.m.