Triple
T20664922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toulouse Metro Line A |
E507858
|
entity |
| Predicate | rollingStock |
P1305
|
FINISHED |
| Object | VAL 206 |
—
|
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: VAL 206 | Statement: [Toulouse Metro Line A, rollingStock, VAL 206]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: VAL 206 Context triple: [Toulouse Metro Line A, rollingStock, VAL 206]
-
A.
VAL 206
chosen
VAL 206 is a type of automated light metro train used on systems such as the Lille Metro’s Line 2.
-
B.
VAL 208
VAL 208 is a type of fully automated, rubber-tyred light metro train used on systems such as the Turin Metro.
-
C.
VA261
VA261 was the final mission of the Ariane 5 ECA heavy-lift launch vehicle, marking the end of Ariane 5’s operational service.
-
D.
VALIC
VALIC is a financial services company specializing in retirement planning and annuity products, operating as a brand of American International Group (AIG).
-
E.
VF-6
VF-6 is a designation commonly used for a U.S. Navy fighter squadron, historically associated with carrier-based aviation units.
- 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_69e0b4c059bc81908ea762cd73ea4424 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6b5c2c6d48190bbfe505cf7d973f9 |
completed | April 20, 2026, 11:24 p.m. |
Created at: April 16, 2026, 11:44 a.m.