Triple
T26692088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stoneley waves |
E672912
|
entity |
| Predicate | attenuationSensitiveTo |
P24994
|
FINISHED |
| Object | fracture connectivity |
—
|
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: fracture connectivity | Statement: [Stoneley waves, attenuationSensitiveTo, fracture connectivity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attenuationSensitiveTo Context triple: [Stoneley waves, attenuationSensitiveTo, fracture connectivity]
-
A.
isAttenuated
Indicates that the strength, intensity, or effect of something has been reduced or weakened relative to a prior or normal state.
-
B.
antennaeSensitivity
Indicates the degree to which an entity’s antennae can detect or respond to external stimuli.
-
C.
lessSensitiveTo
Indicates that one entity exhibits a lower degree of responsiveness or susceptibility to another entity or factor compared to a reference level.
-
D.
sensitivityFeature
chosen
Indicates a relationship where one entity functions as a sensitivity-related characteristic, parameter, or attribute of another entity.
-
E.
isAirSensitive
Indicates that the subject undergoes degradation, reaction, or loss of function upon exposure to air.
- 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_69eecda2066c8190a344218afa5e89c1 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f61fd623bc819091df736cf3419b99 |
completed | May 2, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69f61b3d23f481908dfec27adace900a |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 3:26 a.m.