Triple
T26692055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | P-waves |
E672911
|
entity |
| Predicate | phaseNameInSeismology |
P52575
|
FINISHED |
| Object | P |
—
|
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: P | Statement: [P-waves, phaseNameInSeismology, P]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: phaseNameInSeismology Context triple: [P-waves, phaseNameInSeismology, P]
-
A.
codeNameOfPhase
chosen
Indicates that an entity is assigned a specific code name corresponding to a particular phase in a process or lifecycle.
-
B.
phaseDefinition
Indicates that one entity defines, specifies, or characterizes a particular phase or stage of another entity or process.
-
C.
describesPhase
Indicates that one entity specifies or characterizes the particular phase or stage of another entity or process.
-
D.
phaseType
Indicates the specific stage or phase category that an associated process, event, or lifecycle instance belongs to.
-
E.
PhaseIDescribes
Indicates that one entity provides a description or characterization of a specific phase (Phase I) of another entity or process.
- 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_69f6174310d48190b1ef1e515fed7990 |
completed | May 2, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 3:26 a.m.