Triple
T16089927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prague trams |
E390334
|
entity |
| Predicate | operatedBy |
P86
|
FINISHED |
| Object | DPP |
E1192844
|
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: DPP | Statement: [Prague trams, operatedBy, DPP]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: DPP Context triple: [Prague trams, operatedBy, DPP]
-
A.
DPP
DPP is a centrist political party in Japan known for advocating moderate economic reforms and pragmatic policy positions.
-
B.
DPP
chosen
DPP is the main public transport operator in Prague, responsible for running the city’s metro, trams, and buses.
-
C.
DPP
DPP is the Maryland state agency responsible for supervising individuals on parole and probation and supporting their reintegration into the community.
-
D.
DPP
DPP (Device Provisioning Protocol) is a Wi‑Fi Alliance standard that simplifies and secures the process of adding new devices to a Wi‑Fi network without requiring traditional passwords.
-
E.
DPP
DPP is a major political party in Taiwan known for its generally pro-independence stance and advocacy of progressive, democratic reforms.
- 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_69d87f198bc48190a8b7e53ca15b7ead |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e184522b2c8190986daae6cb2d9db4 |
completed | April 17, 2026, 12:52 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffeb934b448190a486401ac6c01065 |
completed | May 10, 2026, 2:21 a.m. |
Created at: April 10, 2026, 4:59 a.m.