Triple
T19705111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | G-14 |
E473192
|
entity |
| Predicate | shortName |
P43
|
FINISHED |
| Object | G-14 |
—
|
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: G-14 | Statement: [G-14, shortName, G-14]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: G-14 Context triple: [G-14, shortName, G-14]
-
A.
G-14
chosen
G-14 was a former coalition of Europe’s most powerful football clubs that acted as a lobbying group before being superseded by the European Club Association.
-
B.
G-24
G-24 is an intergovernmental group of developing countries that coordinates positions on international monetary and development finance issues.
-
C.
G-1
G-1 is the United States Army staff designation responsible for personnel management, including human resources policies, manpower, and related administrative functions.
-
D.
G.194
G.194 is an ITU-T audio coding standard that specifies techniques for reducing or controlling echo in digital telephone networks.
-
E.
G-2
G-2 is the U.S. Army staff designation for the senior intelligence officer responsible for overseeing military intelligence activities and analysis.
- 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_69d8e516dd048190a0b6c93ea3e71f58 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e642b998608190a82f23bbf77f7bd2 |
completed | April 20, 2026, 3:14 p.m. |
Created at: April 10, 2026, 1:46 p.m.