Triple
T15839679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ginga |
E384068
|
entity |
| Predicate | mainInstrumentType |
P12711
|
FINISHED |
| Object | proportional counter X-ray detector |
—
|
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: proportional counter X-ray detector | Statement: [Ginga, mainInstrumentType, proportional counter X-ray detector]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainInstrumentType Context triple: [Ginga, mainInstrumentType, proportional counter X-ray detector]
-
A.
typeOfInstrument
chosen
Indicates the specific kind or category of instrument associated with an entity.
-
B.
mainInstrumentFeatures
Indicates that the specified features characterize or describe the main instrument involved in an event or context.
-
C.
parentInstrument
Indicates that one instrument serves as the broader, containing, or originating instrument from which another, more specific or derived instrument is related.
-
D.
musicInstrumentation
Indicates the specific instruments or instrumental forces used to perform a piece of music.
-
E.
primaryInstrumentFamily
Indicates the main family or category of musical instruments with which an entity is primarily associated.
- F. None of above.
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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e142e69360819091ea0556bd66d785 |
completed | April 16, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69e005418f588190824d91ff7974dada |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:49 a.m.