Triple
T12271393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Solar–Terrestrial Physics program |
E292477
|
entity |
| Predicate | usesGroundInstrument |
P933
|
FINISHED |
| Object | magnetometer networks |
—
|
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: magnetometer networks | Statement: [International Solar–Terrestrial Physics program, usesGroundInstrument, magnetometer networks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesGroundInstrument Context triple: [International Solar–Terrestrial Physics program, usesGroundInstrument, magnetometer networks]
-
A.
usesInstrument
chosen
Indicates that an agent performs an action by employing a specific instrument or tool as the means to carry it out.
-
B.
playedInstrument
Indicates that an entity performed or used a particular musical instrument.
-
C.
reliesOnInstrument
Indicates that an action or process depends on or is carried out using a particular instrument or tool.
-
D.
hasMusicalInstrument
Indicates that one entity possesses, uses, or is associated with a particular musical instrument.
-
E.
typeOfInstrument
Indicates the specific kind or category of instrument associated with an entity.
- 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_69d6ab6856488190b5d31178d5015f8e |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d9380a5e78819086bd4dfe9a83d1f5 |
completed | April 10, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69d91c4a66cc819083ce6fcaf5042af6 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:52 p.m.