Triple
T17222627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Invalides (Paris) |
E418023
|
entity |
| Predicate | hasSymbol |
P129
|
FINISHED |
| Object | M (Métro symbol) |
E342979
|
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: M (Métro symbol) | Statement: [Invalides (Paris), hasSymbol, M (Métro symbol)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: M (Métro symbol) Context triple: [Invalides (Paris), hasSymbol, M (Métro symbol)]
-
A.
M (Paris Métro symbol)
chosen
M (Paris Métro symbol) is the iconic yellow "M" logo used to mark entrances to the Paris Métro network.
-
B.
Metros
Metros is the nickname historically used for the MetroStars, the former Major League Soccer team now known as the New York Red Bulls.
-
C.
M2 metro line
The M2 metro line is one of Budapest’s main rapid transit lines, running east–west across the city and connecting key residential and commercial districts.
-
D.
MRT
MRT is a common abbreviation for urban metro or subway systems providing high-capacity public transportation in major cities.
-
E.
MRT
MRT is the three-letter ISO 3166-1 alpha-3 country code assigned to Mauritania.
- 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_69d886d779488190b131369541c04e7d |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42ddf2c3c8190b6adceaaefd4ccbf |
completed | April 19, 2026, 1:20 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0167596ab481909df59ce68c7f640e |
completed | May 11, 2026, 5:21 a.m. |
Created at: April 10, 2026, 5:38 a.m.