Triple
T501261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marchantiophyta |
E10405
|
entity |
| Predicate | isVascular |
P10933
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Marchantiophyta, isVascular, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isVascular Context triple: [Marchantiophyta, isVascular, false]
-
A.
usesVesselType
Indicates that an entity performs an activity or operation by employing a specific type or category of vessel.
-
B.
hasVesselType
Indicates that an entity is associated with or classified by a specific type of vessel (e.g., ship, boat, or container).
-
C.
circulation
Indicates the movement or flow of something (such as information, materials, or currency) through a system, network, or among entities.
-
D.
circulatesIn
Indicates that something moves or flows repeatedly within a particular space, system, or medium.
-
E.
hasCirculatorySystem
chosen
Indicates that an entity possesses a circulatory system, i.e., an internal network for transporting blood or equivalent fluids throughout its body.
- 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_69a2e848adf881908e5e04f7af030093 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f131e2148190afd43402f505c73e |
completed | Feb. 28, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69a2edfbb7e0819092cf29c2c68fe8fb |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.