Triple
T16238356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | G (New York City Subway service) |
E394173
|
entity |
| Predicate | originalName |
P65
|
FINISHED |
| Object | GG |
E92816
|
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: GG | Statement: [G (New York City Subway service), originalName, GG]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: GG Context triple: [G (New York City Subway service), originalName, GG]
-
A.
GG
chosen
GG was the original designation for New York City's G subway service, a crosstown line that runs through Brooklyn and Queens without entering Manhattan.
-
B.
GG
GG is the standard abbreviation for Germany’s constitution, the Basic Law for the Federal Republic of Germany.
-
C.
GU
GU is a Japanese casual fashion retail brand known for its affordable, trend-focused clothing and as a sister brand to Uniqlo under the Fast Retailing group.
-
D.
GU
GU is a United Kingdom postcode area covering Guildford and surrounding parts of Surrey and nearby counties.
-
E.
GU
GU is the station code used to identify Guadalupe station within the railway network.
- 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_69d87f2171208190951025e526947816 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2455c7a3c81909e3b42edf03be43e |
completed | April 17, 2026, 2:36 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a000edaf76c8190acc01f58845e570a |
completed | May 10, 2026, 4:51 a.m. |
Created at: April 10, 2026, 5:04 a.m.