Triple
T22910290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JGTO |
E568569
|
entity |
| Predicate | shortName |
P43
|
FINISHED |
| Object | JGTO |
—
|
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: JGTO | Statement: [JGTO, shortName, JGTO]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: JGTO Context triple: [JGTO, shortName, JGTO]
-
A.
JGTO
chosen
JGTO is the organizing body responsible for running and overseeing the professional men's golf tour in Japan.
-
B.
GJT
GJT is the IATA airport code for Grand Junction Regional Airport, a commercial airport serving Grand Junction and western Colorado.
-
C.
TGO
TGO is the three-letter ISO 3166-1 alpha-3 country code assigned to the West African nation of Togo.
-
D.
TGO
TGO is a European-Russian Mars orbiter designed to study trace gases in the Martian atmosphere, particularly methane, to investigate potential geological or biological activity.
-
E.
GTO
GTO is the flashy, talkative driver of a yellow Pontiac GTO who serves as a central, enigmatic foil to the film’s quiet street racers in the 1971 road movie "Two-Lane Blacktop."
- 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_69e2458cd9e48190943ad2e34485d939 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1807350008190a057e8fb5c363c5f |
completed | April 29, 2026, 3:52 a.m. |
Created at: April 17, 2026, 3:42 p.m.