Triple
T10681155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Acipenser |
E251757
|
entity |
| Predicate | evolutionaryCharacteristic |
P40326
|
FINISHED |
| Object | ancient lineage |
—
|
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: ancient lineage | Statement: [Acipenser, evolutionaryCharacteristic, ancient lineage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: evolutionaryCharacteristic Context triple: [Acipenser, evolutionaryCharacteristic, ancient lineage]
-
A.
evolutionaryDescription
Indicates how an entity has changed, adapted, or developed over time through evolutionary processes.
-
B.
biologicalCharacteristic
chosen
Indicates that one entity possesses or exhibits a particular biological trait, feature, or property in relation to another.
-
C.
evolutionaryPosition
Indicates the relative placement of an entity within an evolutionary sequence or lineage, such as its stage, branching point, or order of emergence in evolutionary history.
-
D.
evolutionaryPhase
Indicates the stage or period an entity is in within a broader process of gradual development or evolution.
-
E.
evolvedWith
Indicates that two or more entities have undergone evolutionary change in mutual influence or parallel over time.
- 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_69d6aa5bd7c08190a816e733b4045c23 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fcc1b8d4819082fde22db39d8b24 |
completed | April 9, 2026, 1:11 a.m. |
| PD | Predicate disambiguation | batch_69d6dd8a93208190a573061387e2aebb |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:10 p.m.