Triple
T5407928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SOM I |
E120938
|
entity |
| Predicate | followedBy |
P78
|
FINISHED |
| Object | SOM II |
E22644
|
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: SOM II | Statement: [SOM I, followedBy, SOM II]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SOM II Context triple: [SOM I, followedBy, SOM II]
-
A.
SOM II
chosen
SOM II is the second session in a series of high-level Senior Officials' Meetings where government representatives coordinate and prepare policy and agenda items for ministerial or leaders’ summits.
-
B.
SOM I
SOM I is the first installment in the SOM series, serving as the initial part that precedes SOM II.
-
C.
SOM
SOM is the three-letter ISO 3166-1 alpha-3 country code assigned to Somalia.
-
D.
SoMa
SoMa is a large, formerly industrial neighborhood in San Francisco known for its tech offices, lofts, nightlife, and cultural institutions.
-
E.
SÖM
SÖM is the vehicle registration code for the Sömmerda district in the German state of Thuringia.
- 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_69bd46391c0c81909fa484446732b6a3 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd8793ab3c81909992b257d462a554 |
completed | March 20, 2026, 5:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf33990f248190841493f0720aa8ee |
completed | March 22, 2026, 12:11 a.m. |
Created at: March 20, 2026, 2:05 p.m.