Triple
T343518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pinaceae |
E6887
|
entity |
| Predicate | lifeSpan |
P585
|
FINISHED |
| Object | long-lived perennials |
—
|
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: long-lived perennials | Statement: [Pinaceae, lifeSpan, long-lived perennials]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lifeSpan Context triple: [Pinaceae, lifeSpan, long-lived perennials]
-
A.
lifespan
chosen
Indicates the duration of time between an entity’s birth (or creation) and its death (or end).
-
B.
lifeStage
Indicates the specific phase or period in an entity’s development or lifecycle that it is currently in.
-
C.
lifeDetails
Indicates that additional information or specific aspects about an entity’s life (such as background, experiences, or personal history) are being described.
-
D.
lifeForm
Indicates that an entity is a living organism or belongs to a category of living organisms.
-
E.
supportsLife
Indicates that one entity provides conditions or resources that allow another entity to live, grow, or remain biologically viable.
- 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_69a2e7951ba08190960e90823b5078f3 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eb0019088190a9b969c4287dc4fa |
completed | Feb. 28, 2026, 1:17 p.m. |
| PD | Predicate disambiguation | batch_69a2e9530c98819085025efe4e04aa7e |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.