Triple
T28855754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hydrostachyaceae |
E728728
|
entity |
| Predicate | hasSubmergedHabit |
P194000
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Hydrostachyaceae, hasSubmergedHabit, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubmergedHabit Context triple: [Hydrostachyaceae, hasSubmergedHabit, true]
-
A.
submergedBy
Indicates that one entity is covered or overwhelmed by liquid, typically water, to the point of being beneath its surface due to the action or presence of another entity.
-
B.
hasCauseOfSubmergence
Indicates a relationship where one entity is the cause or reason for another entity becoming submerged or underwater.
-
C.
submerged
Indicates that one entity is located beneath the surface of a liquid or other surrounding medium, typically fully covered by it.
-
D.
submergedForPurpose
Indicates that one entity is intentionally placed or kept under a liquid or surface in order to achieve a specific purpose or outcome.
-
E.
formedBySubmerging
Indicates that something comes into existence or is created as a result of being placed or held beneath the surface of a liquid.
- 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_69f0319f4e5481909e4c439dbe8be940 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fd5d48855c8190bd93070b6a00d8b5 |
completed | May 8, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69fd5c9aabb88190912800d90184a89d |
completed | May 8, 2026, 3:46 a.m. |
| PDg | Predicate description generation | batch_69fd5d47da488190a4f2dbd44a0a83b2 |
completed | May 8, 2026, 3:49 a.m. |
Created at: April 28, 2026, 6:45 a.m.