Triple
T23302412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 3GPP2 |
E590337
|
entity |
| Predicate | coordinatesWith |
P1140
|
FINISHED |
| Object | TTC |
—
|
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: TTC | Statement: [3GPP2, coordinatesWith, TTC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TTC Context triple: [3GPP2, coordinatesWith, TTC]
-
A.
TTC
chosen
TTC is an organizational partner of the 3rd Generation Partnership Project (3GPP), contributing to the development and standardization of mobile telecommunications technologies.
-
B.
TTC
The TTC is a high-level transatlantic forum where the European Union and the United States coordinate on trade, economic, and technology policy issues.
-
C.
TTC
TTC is the national telecommunications provider of Tuvalu, responsible for delivering phone and internet services across the island nation.
-
D.
TTC
TTC is the station code for The Trafford Centre tram stop on Greater Manchester's Metrolink light rail network.
-
E.
TTC network
The TTC network is Toronto’s integrated public transit system, encompassing subway, streetcar, and bus services across the city.
- 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_69e25d1c0ecc8190a355aa229f06d0e0 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1972406a08190bbf355cc7a9f8432 |
completed | April 29, 2026, 5:29 a.m. |
Created at: April 17, 2026, 5:04 p.m.