Triple
T3155587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paris Métro Line 2 |
E65977
|
entity |
| Predicate | rollingStock |
P1305
|
FINISHED |
| Object | MF 01 |
E199145
|
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: MF 01 | Statement: [Paris Métro Line 2, rollingStock, MF 01]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MF 01 Context triple: [Paris Métro Line 2, rollingStock, MF 01]
-
A.
MF 01
chosen
MF 01 is a class of modern steel-wheeled electric multiple unit trains used on several lines of the Paris Métro.
-
B.
MF 77
MF 77 is a steel-wheeled electric multiple unit train used on several lines of the Paris Métro, introduced in the late 1970s to modernize the network’s rolling stock.
-
C.
MF 67
MF 67 is a class of steel-wheeled electric multiple unit trains that have long served as a primary rolling stock type on the Paris Métro.
-
D.
FMF
FMF is the commonly used abbreviation for the Mexican Football Federation, the governing body of professional and amateur soccer in Mexico.
-
E.
MFS
MFS (Macintosh File System) is the original flat file system used by early Macintosh computers before the introduction of the hierarchical HFS.
- 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_69ad8584485081909ed529e890cadc4a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada5e97548819084643586fff2e3cb |
completed | March 8, 2026, 4:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b225068444819080e2b8b6b1260613 |
completed | March 12, 2026, 2:29 a.m. |
Created at: March 8, 2026, 3:05 p.m.