Triple
T4411974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GST |
E94870
|
entity |
| Predicate | countryCodeExample |
P42506
|
FINISHED |
| Object | OM |
E103621
|
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: OM | Statement: [GST, countryCodeExample, OM]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: OM Context triple: [GST, countryCodeExample, OM]
-
A.
OM
OM is the commonly used abbreviation for Olympique de Marseille, a major French professional football club based in Marseille.
-
B.
OM
OM is the post-nominal abbreviation used by members of the Order of Merit, a prestigious British honor recognizing distinguished service in the armed forces, science, art, literature, or the promotion of culture.
-
C.
OM
OM is an American experimental rock band known for its hypnotic, drone-influenced sound and spiritually themed compositions.
-
D.
OM
chosen
OM is the two-letter ISO 3166-1 alpha-2 country code assigned to Oman for international identification and data standards.
-
E.
Om
Om is a sacred sound and spiritual symbol in Hinduism, representing the essence of ultimate reality and the universe.
- 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_69b34539638c8190abfea3eb29425210 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35640269c8190a88fc6b59070561b |
completed | March 13, 2026, 12:11 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b5f6131de08190968259a0be73cd3f |
completed | March 14, 2026, 11:58 p.m. |
Created at: March 12, 2026, 11:29 p.m.