Triple
T22452094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Netherlands Football League Championship |
E555017
|
entity |
| Predicate | countryCode |
P208
|
FINISHED |
| Object | NED |
—
|
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: NED | Statement: [Netherlands Football League Championship, countryCode, NED]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: NED Context triple: [Netherlands Football League Championship, countryCode, NED]
-
A.
NED
chosen
NED is the official FIFA country code used to represent the Netherlands national football team in international competitions and records.
-
B.
NED
NED is the Indian Railways station code for Nanded railway station in Maharashtra, India.
-
C.
NED
NED is the abbreviated title historically used for the early editions of what later became known as the Oxford English Dictionary.
-
D.
NED
NED is an online astronomical database maintained by NASA that compiles and cross-references data on extragalactic objects such as galaxies and quasars.
-
E.
NED
NED is the commonly used abbreviation for the Nuclear Engineering Division, a specialized unit focused on research, development, and applications of nuclear science and engineering.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e11e5113208190ab58c6b595f9d1d0 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15b4c63e88190aeedc326599edd18 |
completed | April 29, 2026, 1:13 a.m. |
Created at: April 16, 2026, 8:48 p.m.