Triple
T4919878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Olympic Committee of Greece |
E110436
|
entity |
| Predicate | hasNationalScope |
P6454
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [National Olympic Committee of Greece, hasNationalScope, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNationalScope Context triple: [National Olympic Committee of Greece, hasNationalScope, yes]
-
A.
hasNationalStatus
Indicates that an entity possesses an official national-level designation, recognition, or status within a country.
-
B.
hasCommitteeScope
Indicates that a committee’s authority, responsibilities, or area of focus extends over a specified domain or subject.
-
C.
hasCountryContext
Indicates that something is associated with, interpreted within, or relevant to a specific country or national context.
-
D.
hasNationalDimension
chosen
Indicates that something possesses a scope, relevance, or impact at the level of a nation or entire country.
-
E.
hasNationalLocationCode
Indicates that an entity is associated with a specific national location code that identifies its location within a country’s coding system.
- 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_69bd4413f9908190afcff44d7929cc4c |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6faa78b88190938bee2f81025083 |
completed | March 20, 2026, 4:02 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3421588190ab08e92b9558042e |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:29 p.m.