Triple
T4065982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DAN |
E86323
|
entity |
| Predicate | senses |
P53283
|
FINISHED |
| Object | neutrons scattered from Martian regolith |
—
|
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: neutrons scattered from Martian regolith | Statement: [DAN, senses, neutrons scattered from Martian regolith]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: senses Context triple: [DAN, senses, neutrons scattered from Martian regolith]
-
A.
sensorySystem
Indicates that one entity functions as the sensory system (or part of it) of another, enabling the detection and processing of internal or external stimuli.
-
B.
primarySense
Indicates that one sense or meaning of an entity is designated as its main or most central sense among possible alternatives.
-
C.
senseOfSmell
Indicates that one entity has the ability to detect or perceive odors or scents through the sense of smell.
-
D.
hasSensoryOrgans
Indicates that an entity possesses organs specialized for sensing or perceiving stimuli from its environment.
-
E.
providesSensoryEffects
Indicates that one entity causes or contributes to sensory experiences or perceptions in another entity.
- 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_69aed93c69208190a4efac0efe3cd69b |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefbf58d9c8190936e453b0d397cb0 |
completed | March 9, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_69aef9061d2481908307cafc9e9b32c0 |
completed | March 9, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69aefa5c52648190b001027f4dba75cb |
completed | March 9, 2026, 4:50 p.m. |
Created at: March 9, 2026, 3:38 p.m.