Triple
T1317835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Olympic Committees |
E28145
|
entity |
| Predicate | mayReceive |
P4382
|
FINISHED |
| Object | financial support from government |
—
|
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: financial support from government | Statement: [National Olympic Committees, mayReceive, financial support from government]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayReceive Context triple: [National Olympic Committees, mayReceive, financial support from government]
-
A.
mayRequest
Indicates that one entity is permitted or authorized to make a request to another entity or for a particular resource or action.
-
B.
mayHold
Indicates that one entity is permitted or allowed to possess, contain, or maintain another entity.
-
C.
receives
chosen
Indicates that one entity is the recipient of something (such as an object, message, or action) from another entity.
-
D.
mayResultIn
Indicates that one entity has the potential to cause, lead to, or bring about another entity or outcome, without guaranteeing that it will occur.
-
E.
mayReportTo
Indicates that one entity is permitted or allowed to have a reporting relationship to another entity, such as an employee being allowed to report to a particular manager.
- 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_69a498532c3481909223b74af2e578df |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c176c89881909e9dc0e34f12f056 |
completed | March 1, 2026, 10:45 p.m. |
| PD | Predicate disambiguation | batch_69a4beebcb348190964bd7215811942c |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:55 p.m.