Triple
T10042011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MTU MB 838 CaM 500 |
E205317
|
entity |
| Predicate | developedBy |
P73
|
FINISHED |
| Object | MTU |
E745146
|
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: MTU | Statement: [MTU MB 838 CaM 500, developedBy, MTU]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MTU Context triple: [MTU MB 838 CaM 500, developedBy, MTU]
-
A.
MTU
MTU is a public research university in Houghton, Michigan, known for its strong engineering, technology, and science programs.
-
B.
MTU
chosen
MTU is a German brand best known for its high-performance diesel engines and propulsion systems used in marine, industrial, and power generation applications.
-
C.
MTC
MTC is the station code for Meerut City railway station, a major rail hub in the city of Meerut, Uttar Pradesh, India.
-
D.
MTC
MTC is a regional planning and transportation agency that coordinates and funds transit, highways, and other mobility projects in the San Francisco Bay Area.
-
E.
MTC
MTC is the three-letter station code used to identify Mornington Crescent tube station on the London Underground 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_69ca834f70e88190b2d74828b7767ec1 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcee48d8c8190af7c93b60f8ca7cb |
completed | April 2, 2026, 2:05 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d29a35fbc081908ec7d359ec3332f2 |
completed | April 5, 2026, 5:21 p.m. |
Created at: March 30, 2026, 8:55 p.m.