Triple
T2330367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GSLV Mk III |
E48387
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | LVM3 |
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 | Statement: [GSLV Mk III, alsoKnownAs, LVM3]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LVM3 Context triple: [GSLV Mk III, alsoKnownAs, LVM3]
-
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.
L3
L3 is a particle physics experiment that operated at CERN’s Large Electron–Positron Collider, designed to study high-energy electron–positron collisions and probe the Standard Model.
-
C.
SL3
SL3 is a branch of Boston’s MBTA Silver Line bus rapid transit system that connects South Station with Chelsea via the Seaport and East Boston tunnels.
-
D.
U3
U3 is one of the main lines of the Nuremberg U-Bahn rapid transit system in Nuremberg, Germany.
-
E.
LMT
LMT is the stock ticker symbol for Lockheed Martin Corporation, a major American aerospace, defense, and security company.
- 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_69a88aa308a88190b0b86c011fda7fce |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc667235c819086140af9db961203 |
completed | March 7, 2026, 6:32 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae8974ab8c81908ec2bddcc882cf42 |
completed | March 9, 2026, 8:48 a.m. |
Created at: March 4, 2026, 7:50 p.m.