Triple
T2015166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regions of Belgium |
E43777
|
entity |
| Predicate | languageCriterion |
P34502
|
FINISHED |
| Object | territorial |
—
|
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: territorial | Statement: [Regions of Belgium, languageCriterion, territorial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageCriterion Context triple: [Regions of Belgium, languageCriterion, territorial]
-
A.
languageStandard
Indicates that one entity conforms to, is defined by, or is governed by the language rules, specifications, or conventions established by another entity as a standard.
-
B.
languageUse
Indicates the language or languages an entity uses for communication, expression, or interaction.
-
C.
languageProvision
Indicates that one entity supplies, supports, or makes available a particular language (or set of languages) for use by another entity.
-
D.
languageDesigned
Indicates that one entity created or developed the language used or associated with another entity.
-
E.
languageForm
Indicates the specific linguistic form or expression in which something is conveyed or represented.
- F. None of above. chosen
Provenance (4 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_69a88716e9f08190946313fdc949e3cf |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb8b610a88190bc10fd7dda19da08 |
completed | March 7, 2026, 5:33 a.m. |
| PD | Predicate disambiguation | batch_69abb7a03a1c81909ad50d56667db2d5 |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb83e7888819096dc40275c77daff |
completed | March 7, 2026, 5:31 a.m. |
Created at: March 4, 2026, 7:37 p.m.