Triple
T11144056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | England national netball team |
E263627
|
entity |
| Predicate | code |
P1537
|
FINISHED |
| Object | ENG |
E144181
|
NE 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: ENG | Statement: [England national netball team, code, ENG]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ENG Context triple: [England national netball team, code, ENG]
-
A.
ENG
chosen
ENG is the three-letter FIFA country code used to represent the England national football team in international competitions and official records.
-
B.
EN
EN is the standard abbreviation used in Portugal for "Estrada Nacional," the national road network.
-
C.
English
English is a widely spoken West Germanic language that serves as a global lingua franca in education, business, science, and international communication.
-
D.
En
En is the Romansh name for the Inn River, a major Alpine river flowing through Switzerland, Austria, and Germany.
-
E.
EngC
EngC is the professional regulatory body that sets and maintains standards for engineering practice and registration in the United Kingdom.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6aa9c0ba08190bbd19c217489b755 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8634d5481909b114d30a542ea3f |
completed | April 9, 2026, 5:56 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e44215513481908909ce4289aabca6 |
completed | April 19, 2026, 2:46 a.m. |
Created at: April 8, 2026, 9:28 p.m.