Triple
T19647570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AGTC |
E471718
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | AGC |
—
|
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: AGC | Statement: [AGTC, relatedTo, AGC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: AGC Context triple: [AGTC, relatedTo, AGC]
-
A.
AGC
AGC is a family of modern French regional multiple-unit trains built by Bombardier for versatile operation on TER networks.
-
B.
AGC
AGC is a leading Japanese manufacturer known worldwide for its glass, electronics, chemicals, and high-tech materials used in buildings, automobiles, and various industrial applications.
-
C.
AGC
AGC is a powerful Colombian neo-paramilitary and drug-trafficking organization widely known for violence, territorial control, and involvement in the cocaine trade.
-
D.
AGC
AGC is the Indian Railways station code for Agra Cantonment railway station, the main rail hub serving the city of Agra in Uttar Pradesh, India.
-
E.
AGC
AGC is an international treaty that coordinates and standardizes the main railway lines across Europe to facilitate efficient cross-border rail transport.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide. chosen
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_69d8e51395348190ac1416d46dfc6db0 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e64125dd9481908a891c71c975a964 |
completed | April 20, 2026, 3:07 p.m. |
Created at: April 10, 2026, 1:44 p.m.