Triple
T15764413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flemish people |
E382180
|
entity |
| Predicate | legalStatusInBelgium |
P120235
|
FINISHED |
| Object | constitutive community |
—
|
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: constitutive community | Statement: [Flemish people, legalStatusInBelgium, constitutive community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalStatusInBelgium Context triple: [Flemish people, legalStatusInBelgium, constitutive community]
-
A.
legalStatusInEuropeanUnion
Indicates the legal status or standing that an entity holds within the jurisdictional framework of the European Union.
-
B.
legalStatusInManyCountries
Indicates that the subject has a particular legal classification or standing that is recognized across numerous countries.
-
C.
positionInBelgium
Indicates that one entity occupies a specific geographic location within the territory of Belgium.
-
D.
hasNameInBelgium
Indicates that an entity is known or referred to by a particular name specifically within the context of Belgium.
-
E.
legalStatusInPortugal
Indicates the legal status or classification that an entity holds specifically within the jurisdiction of Portugal.
- 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_69d86da09a10819082fe9797b23e4664 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e050b6c9fc8190a1bcf763c4b04b12 |
completed | April 16, 2026, 3 a.m. |
| PD | Predicate disambiguation | batch_69e00531e7ac8190a4190cce4f7fab4c |
completed | April 15, 2026, 9:37 p.m. |
| PDg | Predicate description generation | batch_69e03cc871d0819085c0fc54de7984ff |
completed | April 16, 2026, 1:35 a.m. |
Created at: April 10, 2026, 4:47 a.m.