Triple
T11550123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STIB-MIVB |
E273867
|
entity |
| Predicate | cooperatesWith |
P435
|
FINISHED |
| Object | TEC |
E534795
|
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: TEC | Statement: [STIB-MIVB, cooperatesWith, TEC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TEC Context triple: [STIB-MIVB, cooperatesWith, TEC]
-
A.
TEC
TEC is the commonly used acronym for the Episcopal Church, a mainline Anglican Christian denomination based in the United States.
-
B.
TEC
chosen
TEC is a public transport company in Belgium that operates regional bus and other transit services, primarily in the Walloon region.
-
C.
TEC
TEC is the abbreviation for the Transatlantic Economic Council, a high-level forum for coordinating economic policy and regulatory cooperation between the United States and the European Union.
-
D.
T-MEC
T-MEC is the Spanish-language name for the United States–Mexico–Canada Agreement, the trade pact that replaced NAFTA in North America.
-
E.
TEQ
TEQ is the IATA airport code for Tekirdağ Çorlu Airport in Çorlu, Turkey.
- 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d88a83f1e88190aabf11a4c8a6c9e5 |
completed | April 10, 2026, 5:28 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e6e8396ed081909bdf381db3dacd62 |
completed | April 21, 2026, 3 a.m. |
Created at: April 8, 2026, 9:37 p.m.