Triple
T26530037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plasma Diagnostics Package |
E670793
|
entity |
| Predicate | carriedInstrumentType |
P12711
|
FINISHED |
| Object | electric field sensors |
—
|
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: electric field sensors | Statement: [Plasma Diagnostics Package, carriedInstrumentType, electric field sensors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: carriedInstrumentType Context triple: [Plasma Diagnostics Package, carriedInstrumentType, electric field sensors]
-
A.
carriedInstrument
Indicates that one entity transported or bore a musical instrument with them.
-
B.
carriesInstrument
Indicates that one entity is physically transporting or holding a musical instrument.
-
C.
carriesInstrumentProvidedBy
Indicates that an entity is carrying an instrument that was supplied or provided by another specified entity.
-
D.
carriedInstrumentsFrom
Indicates that an entity transported or bore instruments from a specified source or location to another context or destination.
-
E.
typeOfInstrument
chosen
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_69eeb31ea1e08190b9ff43cf9bc25bf8 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620debeb48190b7db395fb86cf8d9 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 1:34 a.m.