Triple
T10845796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Launch Vehicle Mark 3 |
E256004
|
entity |
| Predicate | marketedAs |
P1395
|
FINISHED |
| Object | LVM3-M2 |
E238215
|
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: LVM3-M2 | Statement: [Launch Vehicle Mark 3, marketedAs, LVM3-M2]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LVM3-M2 Context triple: [Launch Vehicle Mark 3, marketedAs, LVM3-M2]
-
A.
LVM3
chosen
LVM3 is India’s heavy-lift launch vehicle developed by ISRO to carry large communication and deep-space satellites into orbit.
-
B.
M-3
M-3 is a designated highway route, commonly known by its short name M-3, within a regional or national road network.
-
C.
M3
M3 is a circular line of the Copenhagen Metro that loops around the city center, connecting key districts and interchange stations.
-
D.
M3
M3 is one of the main lines of the Bucharest Metro rapid transit system, serving key residential and commercial areas of Romania’s capital.
-
E.
M3
M3 is a boat line that operates as part of Geneva’s public transport network, providing passenger service across the city’s lake or waterways.
- 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_69d6aa81a5d08190aa86689061d1ddd2 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d750d132e081909c977b3dc4110ca4 |
completed | April 9, 2026, 7:10 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69dff7cc0d648190afb0ce80bac7f3dc |
completed | April 15, 2026, 8:40 p.m. |
Created at: April 8, 2026, 9:19 p.m.