Triple
T9837973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pragyan |
E239150
|
entity |
| Predicate | launchVehicle |
P4020
|
FINISHED |
| Object | LVM3 M4 |
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 M4 | Statement: [Pragyan, launchVehicle, LVM3 M4]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LVM3 M4 Context triple: [Pragyan, launchVehicle, LVM3 M4]
-
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-4
M-4 is a major Russian federal highway that runs from Moscow to the Black Sea coast, serving as a key transport corridor in the country.
-
C.
M-3
M-3 is a designated highway route, commonly known by its short name M-3, within a regional or national road network.
-
D.
M4
M4 is a general-purpose macro processing language and preprocessor commonly used in Unix-like build systems and tools such as GNU Autoconf.
-
E.
M4
M4 is one of the lines of the Bucharest Metro rapid transit system, serving several northern and northwestern districts of Romania’s capital.
- 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_69ca84e314108190978324a4bdb959f8 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb347ff4c81908c312548a25bae71 |
completed | April 2, 2026, 12:07 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1e429682c8190a94339b96d4081f6 |
completed | April 5, 2026, 4:25 a.m. |
Created at: March 30, 2026, 8:33 p.m.