Triple
T13046237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OPU |
E327330
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | OPU |
E327330
|
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: OPU | Statement: [OPU, abbreviation, OPU]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: OPU Context triple: [OPU, abbreviation, OPU]
-
A.
OPU
chosen
OPU is the central executive office that supports and coordinates the work of the President of Ukraine.
-
B.
OPAL
OPAL is the abbreviation for the American Society of Civil Engineers' prestigious Outstanding Projects and Leaders Award, which honors exceptional achievements and leadership in civil engineering.
-
C.
OPAL
OPAL was one of the major particle physics experiments at CERN’s Large Electron–Positron Collider, designed to study electron-positron collisions and probe the Standard Model.
-
D.
OPO
OPO is the vehicle registration code assigned to the Polish city of Opole.
-
E.
OPO
OPO is the IATA airport code for Francisco Sá Carneiro Airport, the main international airport serving Porto, Portugal.
- 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_69d8076e64308190904fb5c93517c901 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d9805125e481908ed56f708de98a9e |
completed | April 10, 2026, 10:57 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6cbd8f1308190992c0bd832e1b05e |
completed | May 3, 2026, 4:15 a.m. |
Created at: April 9, 2026, 8:56 p.m.