Triple
T9516183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DAN on Curiosity rover |
E229530
|
entity |
| Predicate | usesInActiveMode |
P11331
|
FINISHED |
| Object | pulsed neutron generator |
—
|
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: pulsed neutron generator | Statement: [DAN on Curiosity rover, usesInActiveMode, pulsed neutron generator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesInActiveMode Context triple: [DAN on Curiosity rover, usesInActiveMode, pulsed neutron generator]
-
A.
usedOnMode
chosen
Indicates that something is applied, operated, or functions specifically in a given mode or operational setting.
-
B.
isInUse
Indicates that an entity is currently being utilized or actively engaged in its intended function or operation.
-
C.
usedInState
Indicates that something is employed, applied, or functions within a particular state or condition.
-
D.
usageStatus
Indicates the current state or condition of how something is being used, such as whether it is active, inactive, available, or in use.
-
E.
isPotentiallyActive
Indicates that an entity has the capacity or conditions to become active, but is not necessarily active at the present moment.
- 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_69ca84777560819084cddd999badc1aa |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd987eefec8190b0db1928776bf02b |
completed | April 1, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69cca56a3d088190bdc16670678fb6c6 |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 7:58 p.m.