Triple
T9652211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tarsiiformes |
E233361
|
entity |
| Predicate | evolutionaryPosition |
P89438
|
FINISHED |
| Object | early-diverging haplorrhine primates |
—
|
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: early-diverging haplorrhine primates | Statement: [Tarsiiformes, evolutionaryPosition, early-diverging haplorrhine primates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: evolutionaryPosition Context triple: [Tarsiiformes, evolutionaryPosition, early-diverging haplorrhine primates]
-
A.
evolutionaryPhase
Indicates the stage or period an entity is in within a broader process of gradual development or evolution.
-
B.
evolutionaryDescription
Indicates how an entity has changed, adapted, or developed over time through evolutionary processes.
-
C.
evolutionControlledBy
Indicates that the process or course of evolution of an entity is directed, regulated, or determined by another entity.
-
D.
evolvedWith
Indicates that two or more entities have undergone evolutionary change in mutual influence or parallel over time.
-
E.
evolvesIn
Indicates that an entity undergoes a process of change or development within a specified environment, context, or medium.
- 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_69ca848b31648190b57aa55da20285be |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9bb0cce88190b7eacc8b43450d7f |
completed | April 1, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b0263081908cf6df3eb07d71b0 |
completed | April 1, 2026, 8:22 a.m. |
| PDg | Predicate description generation | batch_69ccd9408c848190b84dd74d87f76273 |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:13 p.m.