Triple
T9805227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Telewizja Polska |
E237937
|
entity |
| Predicate | hasChannel |
P8080
|
FINISHED |
| Object | TVP3 |
E331132
|
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: TVP3 | Statement: [Telewizja Polska, hasChannel, TVP3]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TVP3 Context triple: [Telewizja Polska, hasChannel, TVP3]
-
A.
TVP
chosen
TVP is Poland’s national public television broadcaster, operating multiple channels and services across the country.
-
B.
Tiv
The Tiv are an ethnic group primarily found in central Nigeria, known for their rich agricultural traditions, distinctive language, and vibrant cultural festivals.
-
C.
VOTV
VOTV is the ICAO airport code for Trivandrum International Airport, a major airport serving Thiruvananthapuram in the Indian state of Kerala.
-
D.
PVR
PVR is the IATA airport code for Licenciado Gustavo Díaz Ordaz International Airport serving Puerto Vallarta, Mexico.
-
E.
TVM-300
TVM-300 is a high-speed railway cab signalling and train control system used on French high-speed lines such as the LGV Nord.
- 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_69ca84dd4608819097ff4ed00feca280 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdab7b67748190ba16ce868f29d13e |
completed | April 1, 2026, 11:34 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1c45878e481908aa2098eceb44256 |
completed | April 5, 2026, 2:09 a.m. |
Created at: March 30, 2026, 8:29 p.m.