Triple
T26692078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stoneley waves |
E672912
|
entity |
| Predicate | existIf |
P67472
|
FINISHED |
| Object | specific boundary conditions at the interface are met |
—
|
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: specific boundary conditions at the interface are met | Statement: [Stoneley waves, existIf, specific boundary conditions at the interface are met]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: existIf Context triple: [Stoneley waves, existIf, specific boundary conditions at the interface are met]
-
A.
existsIf
chosen
Indicates that the existence or validity of one entity or condition depends on the presence or truth of another specified condition.
-
B.
existsAs
Indicates that one entity has the same identity or manifestation as another, effectively asserting they are the same existing thing or state.
-
C.
existsFrom
Indicates that an entity comes into existence or begins to be valid starting from a specified point in time or condition.
-
D.
existsFor
Indicates that something is present, available, or holds true for a particular entity, context, or condition.
-
E.
existsBecauseOf
Indicates that one entity’s existence is caused, enabled, or brought about by another 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_69eecda2066c8190a344218afa5e89c1 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f61a17a7788190946f7e32d63cd43f |
completed | May 2, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69f611ab768c8190b1849c15a3e59dda |
completed | May 2, 2026, 3 p.m. |
Created at: April 27, 2026, 3:26 a.m.