Triple
T27703628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Province of Brabant |
E698491
|
entity |
| Predicate | languageBorder |
P17190
|
FINISHED |
| Object | crossed Belgian language frontier |
—
|
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: crossed Belgian language frontier | Statement: [Province of Brabant, languageBorder, crossed Belgian language frontier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageBorder Context triple: [Province of Brabant, languageBorder, crossed Belgian language frontier]
-
A.
languageBorderInvolved
chosen
Indicates that a situation, event, or relationship involves or is affected by a boundary between different languages or linguistic communities.
-
B.
languageAlongBorder
Indicates that a particular language is spoken or prevalent along the border between two regions or entities.
-
C.
borderText
Indicates that one entity is the textual content displayed along the border of another entity.
-
D.
borderColor
Indicates the color that forms the boundary or outline of an entity.
-
E.
recognizedBorder
Indicates that one entity formally acknowledges and accepts another entity’s boundary as a legitimate border.
- 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_69ef590ea74081908f0cd7500d85fa27 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69fd57ba740c8190bd1d40166fccccb7 |
completed | May 8, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69fd55ee82b881908a639da3a41b3af6 |
completed | May 8, 2026, 3:18 a.m. |
Created at: April 27, 2026, 2:58 p.m.