Triple
T27091413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cope’s rule |
E686176
|
entity |
| Predicate | notUniversallyObservedIn |
P9443
|
FINISHED |
| Object | all clades |
—
|
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: all clades | Statement: [Cope’s rule, notUniversallyObservedIn, all clades]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notUniversallyObservedIn Context triple: [Cope’s rule, notUniversallyObservedIn, all clades]
-
A.
notObservedIn
chosen
Indicates that a particular entity, event, or property has not been detected, recorded, or seen within a specified context, dataset, or environment.
-
B.
notObservedBy
Indicates that an entity, event, or condition is not detected, recorded, or perceived by a specified observer or observation process.
-
C.
notObservedOn
Indicates that a particular entity, event, or condition was explicitly not observed or recorded at a specified time or context.
-
D.
notOfficiallyObservedBy
Indicates that an event, phenomenon, or entity has not been formally recorded, monitored, or acknowledged by the specified observer or authority.
-
E.
notFullyAdoptedIn
Indicates that something has not been completely or universally implemented, accepted, or put into practice within a specified context or domain.
- 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_69f62349888081908305958558907967 |
completed | May 2, 2026, 4:16 p.m. |
| PD | Predicate disambiguation | batch_69f61b40f02081909bd9c3ea73249163 |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 8:41 a.m.