Triple
T32212486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TMC 2 |
E822844
|
entity |
| Predicate | heritageInstrument |
P186974
|
FINISHED |
| Object | TMC on Chandrayaan-1 |
—
|
LITERAL 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: TMC on Chandrayaan-1 | Statement: [TMC 2, heritageInstrument, TMC on Chandrayaan-1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heritageInstrument Context triple: [TMC 2, heritageInstrument, TMC on Chandrayaan-1]
-
A.
traditionalInstrument
Indicates that an entity is a musical instrument associated with the traditional or customary music of a particular culture, region, or community.
-
B.
musicInstrumentation
Indicates the specific instruments or instrumental forces used to perform a piece of music.
-
C.
studiedByInstrument
Indicates that something is examined, measured, or analyzed through the use of a specific instrument or device.
-
D.
notableInstrument
Indicates that an entity is especially known for playing or being associated with a particular musical instrument.
-
E.
playedInstrument
Indicates that an entity performed or used a particular musical instrument.
- F. None of above. chosen
Provenance (4 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_69f3490a3bec819097bc58d4731b9d08 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
| PDg | Predicate description generation | batch_69fb2e9309fc81909dfefd9020d6fbad |
completed | May 6, 2026, 12:05 p.m. |
Created at: May 1, 2026, 12:37 a.m.