Triple
T5807404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flemish Brabant |
E128778
|
entity |
| Predicate | hasArrondissements |
P26130
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [Flemish Brabant, hasArrondissements, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArrondissements Context triple: [Flemish Brabant, hasArrondissements, 2]
-
A.
hasArrondissement
chosen
Indicates a relationship where an administrative unit or locality is associated with, or belongs to, a specific arrondissement.
-
B.
hasCommune
Indicates a relationship where an entity is associated with, belongs to, or is located within a specific commune (municipal administrative unit).
-
C.
administrativeDistricts
Indicates that one entity serves as an administrative district or subdivision governed or managed by another entity.
-
D.
belongsToIntercommunality
Indicates that an entity is a member of, or administratively attached to, a specific intercommunal structure or grouping.
-
E.
regionOfCity
Indicates that a specified area or district is a constituent part or subdivision of a particular city.
- 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_69c0084788848190bcf71f6bc5d71597 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02b17417081908779741b9bfbb720 |
completed | March 22, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69c021d5ecd081908a62dd66e26f8598 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:52 p.m.