Triple
T17427365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charleroi Metro |
E423773
|
entity |
| Predicate | owner |
P347
|
FINISHED |
| Object | TEC |
—
|
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: TEC | Statement: [Charleroi Metro, owner, TEC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TEC Context triple: [Charleroi Metro, owner, 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.
Tehkal
Tehkal is a neighborhood and administrative area within the city of Peshawar in Pakistan’s Khyber Pakhtunkhwa province.
-
E.
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.
- 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_69d889d88b6081908bada047f5b3ba51 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e448fdc1348190985db52c8c74c394 |
completed | April 19, 2026, 3:16 a.m. |
Created at: April 10, 2026, 5:46 a.m.