Triple
T7570513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rayleigh waves |
E179226
|
entity |
| Predicate | propagateAlong |
P77529
|
FINISHED |
| Object | Earth's surface |
—
|
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: Earth's surface | Statement: [Rayleigh waves, propagateAlong, Earth's surface]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: propagateAlong Context triple: [Rayleigh waves, propagateAlong, Earth's surface]
-
A.
propagateAt
Indicates that an effect, signal, or influence spreads or is transmitted to a specific location, time, or context.
-
B.
propagationMethod
Indicates the means or mechanism by which something spreads, reproduces, or is transmitted from one entity or location to another.
-
C.
definedAlong
Indicates that one entity is specified, established, or determined in relation to the course, boundary, or extent of another entity.
-
D.
passedAlongside
Indicates that one entity moved or traveled next to another entity along the same route or path, maintaining a roughly parallel course.
-
E.
propagatorType
Indicates the specific method or model used to propagate or advance a state (such as position, condition, or effect) from one point in time or space to another.
- 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_69c69f316e50819081a271c85c06f918 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f920540c8190817712db5aa3eeff |
completed | March 27, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69c6f4de77048190b8769e717fdcf8e7 |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f5b1a6a08190b9ff2bc8a7befe0d |
completed | March 27, 2026, 9:25 p.m. |
Created at: March 27, 2026, 3:51 p.m.