Triple
T1713912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PS |
E37246
|
entity |
| Predicate | representsCommunity |
P21358
|
FINISHED |
| Object | French-speaking Belgians |
—
|
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: French-speaking Belgians | Statement: [PS, representsCommunity, French-speaking Belgians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representsCommunity Context triple: [PS, representsCommunity, French-speaking Belgians]
-
A.
includesCommunity
Indicates that one entity encompasses, contains, or has within it a particular community as part of its scope or composition.
-
B.
supportsCommunity
Indicates that one entity provides assistance, resources, or encouragement that benefits a community or group.
-
C.
associatedCommunity
chosen
Indicates a relationship where an entity is linked or connected to a particular community with which it is involved or identified.
-
D.
formsBiStateCommunityWith
Indicates that two entities jointly constitute or participate in a shared bi-state community spanning both of their jurisdictions.
-
E.
hasCommunityIn
Indicates that a community is present, active, or established within a specified location, platform, or context.
- 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_69a8861912dc8190931af43b4b9158a7 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69ab7521878c8190b9e7739b8c3fc705 |
completed | March 7, 2026, 12:45 a.m. |
| PD | Predicate disambiguation | batch_69aa61bd46d48190915500d75a9d8e94 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:30 p.m.