Triple
T37360377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NOC*NSF |
E927559
|
entity |
| Predicate | abbreviationExplanation |
P43
|
FINISHED |
| Object | NOC stands for Nederlands Olympisch Comité |
—
|
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: NOC stands for Nederlands Olympisch Comité | Statement: [NOC*NSF, abbreviationExplanation, NOC stands for Nederlands Olympisch Comité]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: abbreviationExplanation Context triple: [NOC*NSF, abbreviationExplanation, NOC stands for Nederlands Olympisch Comité]
-
A.
abbreviation
chosen
Indicates that one term is a shortened or contracted form that stands for another, longer expression.
-
B.
abbreviationUsedFor
Indicates that a particular shortened form or acronym is used to represent or stand in for a longer term, name, or expression.
-
C.
abbreviationOrShortForm
Indicates that one term is an abbreviation or shortened form of another term.
-
D.
abbreviationRefersTo
Indicates that an abbreviation stands for or denotes the full form or concept it is associated with.
-
E.
abbreviationUsedBy
Indicates that a particular abbreviation is employed or adopted by a specified entity in its communication, documentation, or usage.
- 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_69f76eb701788190b40824bc4594d985 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb8c38a9688190be524246f5682107 |
completed | May 6, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9c6e0481908565bd849e869b24 |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:16 p.m.