Triple
T20776261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Group on Services |
E511361
|
entity |
| Predicate | acronym |
P43
|
FINISHED |
| Object | GOS |
—
|
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: GOS | Statement: [Group on Services, acronym, GOS]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: GOS Context triple: [Group on Services, acronym, GOS]
-
A.
GOS
GOS is the abbreviation for the Grand Orient of Spain, a major Masonic obedience historically active in Spanish Freemasonry.
-
B.
GOS
chosen
GOS is the acronym for the Global Observing System, an international network of instruments and facilities that continuously monitor the Earth's atmosphere, oceans, and land for weather and climate services.
-
C.
GOSS
GOSS is the ICAO airport code for Saint-Louis Airport in Senegal, used in international aviation for flight planning and air traffic control.
-
D.
Goc
Goc is a German surname most notably associated with professional ice hockey players such as Marcel Goc.
-
E.
GOU
GOU is the Russian abbreviation for the Main Operations Directorate, the key operational command and planning body of the Russian General Staff.
- 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_69e0b4cac7a48190a715cb3d545df2b4 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c26b06ac81909aef3b0a0ad79a33 |
completed | April 21, 2026, 12:18 a.m. |
Created at: April 16, 2026, 12:37 p.m.