Triple
T9672642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cathaya argyrophylla |
E234065
|
entity |
| Predicate | hasRelictStatus |
P40020
|
FINISHED |
| Object | Tertiary relict |
—
|
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: Tertiary relict | Statement: [Cathaya argyrophylla, hasRelictStatus, Tertiary relict]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelictStatus Context triple: [Cathaya argyrophylla, hasRelictStatus, Tertiary relict]
-
A.
hasRelicsStatus
Indicates that an entity holds a particular status or condition specifically related to relics.
-
B.
isRelictLineage
chosen
Indicates that an entity represents a surviving remnant of an otherwise extinct evolutionary lineage.
-
C.
containsRelic
Indicates that one entity holds, includes, or has within it a relic.
-
D.
hasRelicType
Indicates that an entity is associated with, classified by, or possesses a specific type or category of relic.
-
E.
hasSurvivalStatus
Indicates the survival condition or outcome associated with an entity, such as whether it is alive, deceased, or in another defined survival state.
- 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_69ca848f55e48190b3f67252571c3d45 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9c6aa01c819083fc758470096ec2 |
completed | April 1, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b5d40c8190850ad7a351445f32 |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:15 p.m.