Triple
T6333456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avicennia officinalis |
E142434
|
entity |
| Predicate | hasRootType |
P70909
|
FINISHED |
| Object | pneumatophore roots |
—
|
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: pneumatophore roots | Statement: [Avicennia officinalis, hasRootType, pneumatophore roots]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRootType Context triple: [Avicennia officinalis, hasRootType, pneumatophore roots]
-
A.
hasWellAtRoot
Indicates that an entity possesses or has a well located at its root or base.
-
B.
hasNodeType
Indicates that an entity is associated with, or classified as, a specific type of node within a structured system or model.
-
C.
hasTypeSystem
Indicates that an entity employs, is governed by, or is associated with a particular type system (a defined set of rules for classifying and constraining types).
-
D.
hasRootElement
Indicates that one entity is the primary or top-level element from which the structure or hierarchy of another entity originates.
-
E.
hasRouteType
Indicates that there is a specific kind or category of route associated with an entity (e.g., road, rail, bus line).
- 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_69c008d4d8e88190ad301c05b08722ac |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06517a1e88190a0bfcac8a7e3a305 |
completed | March 22, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69c060e7e2d48190af9d004236466788 |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c064c080148190a7c3218867f1f572 |
completed | March 22, 2026, 9:53 p.m. |
Created at: March 22, 2026, 4:30 p.m.