Triple
T28721197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2010–2011 Belgian government formation crisis |
E730098
|
entity |
| Predicate | capitalInvolved |
P180027
|
FINISHED |
| Object | Brussels |
—
|
NE NERFINISHED |
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: Brussels | Statement: [2010–2011 Belgian government formation crisis, capitalInvolved, Brussels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalInvolved Context triple: [2010–2011 Belgian government formation crisis, capitalInvolved, Brussels]
-
A.
totalInvestment
Indicates the overall amount of resources (typically money) committed to a particular entity, project, or activity, aggregating all individual investments involved.
-
B.
capitalSince
Indicates that an entity has served as the capital of another entity starting from a specified point in time.
-
C.
amountInvolvedApprox
Indicates that the relationship specifies an approximate value or quantity involved in an action, event, or transaction.
-
D.
usedCapital
Indicates that an entity made use of a particular capital city as its seat of government or primary administrative center.
-
E.
capitalAtBeginning
Indicates that a string or word has a capital (uppercase) letter as its first character.
- 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_69f043e91fe48190b73bcd8e08d433e0 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
| PDg | Predicate description generation | batch_69f730890a008190a882f7828f1c9162 |
completed | May 3, 2026, 11:24 a.m. |
Created at: April 28, 2026, 5:53 a.m.