Triple
T16916825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Officer Commanding-in-Chief of Army Commands (India) |
E410341
|
entity |
| Predicate | hasAbbreviation |
P43
|
FINISHED |
| Object | GOC-in-C |
E1192332
|
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: GOC-in-C | Statement: [General Officer Commanding-in-Chief of Army Commands (India), hasAbbreviation, GOC-in-C]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: GOC-in-C Context triple: [General Officer Commanding-in-Chief of Army Commands (India), hasAbbreviation, GOC-in-C]
-
A.
GOC-in-C
chosen
GOC-in-C is the title used for the senior-most General Officer Commanding-in-Chief who heads each of the major Army Commands in India.
-
B.
GOC
GOC is the standardised set of spelling and writing rules used for modern Scottish Gaelic.
-
C.
Goc
Goc is a German surname most notably associated with professional ice hockey players such as Marcel Goc.
-
D.
GOJ
GOJ is the IATA airport code for Strigino International Airport serving Nizhny Novgorod, Russia.
-
E.
GCON
GCON is a high-ranking Nigerian national honor, the Grand Commander of the Order of the Niger, awarded for exceptional service to the country.
- 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_69d886c7b1e481908c3766dfa8c13458 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3ca413c408190b3d0af9993b7b825 |
completed | April 18, 2026, 6:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00c7c0cb08819098e2ce2aed4d51b3 |
completed | May 10, 2026, 6 p.m. |
Created at: April 10, 2026, 5:30 a.m.