Triple
T19970943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | COIB |
E480070
|
entity |
| Predicate | BOIC |
P138084
|
FINISHED |
| Object | Dutch acronym for the Belgian National Olympic Committee |
—
|
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: Dutch acronym for the Belgian National Olympic Committee | Statement: [COIB, BOIC, Dutch acronym for the Belgian National Olympic Committee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BOIC Context triple: [COIB, BOIC, Dutch acronym for the Belgian National Olympic Committee]
-
A.
by
Indicates that an action is performed, caused, or authored through the agency, means, or proximity of a specified entity.
-
B.
B_0
Indicates a basic or unspecified binary relationship between two entities, where the exact nature of the connection is not further defined.
-
C.
B_1
Indicates that one entity is the first or primary instance/member in an ordered series or group relative to another entity.
-
D.
bando
Indicates a relationship where an entity is placed under a ban, prohibition, or outlaw status imposed by some authority.
-
E.
bore
Indicates that one entity caused another entity to feel uninterested, tired, or lacking in engagement.
- 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_69d8e523c19881909f9197037200dde6 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65bc89b508190879d29bef546aac8 |
completed | April 20, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69e537f7e4848190b431a69ec3f1b609 |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c42c688190a22f4d31ec692377 |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 10, 2026, 1:54 p.m.