Triple
T18563556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supplementary Multilingual Plane |
E453705
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | SMP |
—
|
NE NERFINISHED |
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: SMP | Statement: [Supplementary Multilingual Plane, abbreviation, SMP]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SMP Context triple: [Supplementary Multilingual Plane, abbreviation, SMP]
-
A.
SMP
chosen
SMP is the Supplementary Multilingual Plane of Unicode, a range of code points used to encode historic scripts, musical notation, and various specialized symbols beyond the Basic Multilingual Plane.
-
B.
SMP
SMP was a Finnish populist agrarian political party that represented rural and small-farmer interests, particularly from the 1950s to the 1990s.
-
C.
SPL
SPL is the commonly used abbreviation for the Scottish Premier League, the former top professional football division in Scotland.
-
D.
SPL
SPL is the Search Processing Language used in Splunk for querying, analyzing, and visualizing machine-generated data.
-
E.
SPL
SPL is a research laboratory focused on developing and testing advanced space propulsion technologies.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53afc57448190abd90167d7e12a18 |
completed | April 19, 2026, 8:28 p.m. |
Created at: April 10, 2026, 11:42 a.m.