Triple
T13389494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hawaiian |
E319537
|
entity |
| Predicate | lavaFlowMorphology |
P17576
|
FINISHED |
| Object | pahoehoe lava |
—
|
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: pahoehoe lava | Statement: [Hawaiian, lavaFlowMorphology, pahoehoe lava]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lavaFlowMorphology Context triple: [Hawaiian, lavaFlowMorphology, pahoehoe lava]
-
A.
geomorphologicalProcess
Indicates a relationship where one entity undergoes or is shaped by natural earth-surface processes that modify landforms and terrain structure.
-
B.
modifiesMorphologyOf
Indicates that one entity alters or changes the morphological structure or form of another entity.
-
C.
hasLavaFlow
chosen
Indicates that one entity exhibits, contains, or is associated with a flow of lava originating from volcanic activity.
-
D.
lavaFlowDestination
Indicates the location or feature toward which a lava flow moves or ultimately comes to rest.
-
E.
morphologicalComparison
Indicates a relationship where two or more entities are compared based on differences or similarities in their morphological (form or structural) characteristics.
- 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_69d806b886bc8190b676e7768b8e01c5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dba0d543348190a9c1be509b015c0f |
completed | April 12, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a03189908190a784a2755f8d81e1 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:34 p.m.