Triple
T27091420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cope’s rule |
E686176
|
entity |
| Predicate | analyzedWith |
P104001
|
FINISHED |
| Object | statistical models of trait evolution |
—
|
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: statistical models of trait evolution | Statement: [Cope’s rule, analyzedWith, statistical models of trait evolution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: analyzedWith Context triple: [Cope’s rule, analyzedWith, statistical models of trait evolution]
-
A.
hasAnalysis
Indicates that an entity is associated with, or has undergone, a particular analysis or examination.
-
B.
analyzes
Indicates that one entity systematically examines or evaluates another entity to understand its nature, structure, or components.
-
C.
helpsAnalyze
Indicates that one entity assists another in examining, interpreting, or understanding something in a more detailed or effective way.
-
D.
oftenAnalyzedIn
Indicates that something is frequently examined, studied, or evaluated within a particular context, field, or framework.
-
E.
analysisType
chosen
Indicates the specific kind or category of analysis being applied or performed in relation to an entity or dataset.
- 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_69ef148940ec819097b5c20fbfbf7c81 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641dc8ff48190ab575d855616580c |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 8:41 a.m.