Triple
T216754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dispute Settlement Understanding |
E4120
|
entity |
| Predicate | hasAbbreviation |
P43
|
FINISHED |
| Object | DSU |
E27701
|
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: DSU | Statement: [Dispute Settlement Understanding, hasAbbreviation, DSU]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: DSU Context triple: [Dispute Settlement Understanding, hasAbbreviation, DSU]
-
A.
DSU
chosen
DSU is the World Trade Organization’s legal framework that sets out the rules and procedures for resolving trade disputes between member countries.
-
B.
DS
DS is the Directorate of Support, a key administrative and logistical branch responsible for providing essential support services within an intelligence or governmental organization.
-
C.
DS
DS is the standardized Diploma Supplement used across the European Higher Education Area to provide transparent, comparable information about higher education qualifications.
-
D.
SU
SU was the two-letter country code used to represent the former Soviet Union in various international standards and systems.
-
E.
NSO
NSO is the commonly used abbreviation for the National Symphony Orchestra, a major American orchestra based in Washington, D.C.
- 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_69a2573508588190b522c2476d91acfe |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25c4edfa081909fe97c86c3c7801d |
completed | Feb. 28, 2026, 3:09 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a34766506c8190a4c661410e0d8b33 |
completed | Feb. 28, 2026, 7:52 p.m. |
Created at: Feb. 28, 2026, 2:53 a.m.