Triple
T33314521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gloger’s rule |
E852977
|
entity |
| Predicate | oftenTestedUsing |
P86589
|
FINISHED |
| Object | museum specimen data |
—
|
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: museum specimen data | Statement: [Gloger’s rule, oftenTestedUsing, museum specimen data]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenTestedUsing Context triple: [Gloger’s rule, oftenTestedUsing, museum specimen data]
-
A.
theoryTested
Indicates that a theory has been subjected to evaluation or experimentation to assess its validity or accuracy.
-
B.
testedWith
chosen
Indicates that one entity has been examined, evaluated, or verified using another entity as the test method, tool, or counterpart.
-
C.
isUsedToTest
Indicates that one entity serves as a means or tool for evaluating, examining, or verifying another entity.
-
D.
testedFor
Indicates that an entity has been examined or analyzed to determine the presence, absence, or level of another specified entity or condition.
-
E.
testedAs
Indicates that one entity has been evaluated, examined, or subjected to a test in the role or capacity of another specified entity or condition.
- 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_69f349679fd8819093b9b40e989440e3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd231cab588190ad0953dc8f4af8f2 |
completed | May 7, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69fd1aa3f1c481909fe6e9cab1383551 |
completed | May 7, 2026, 11:05 p.m. |
Created at: May 1, 2026, 1:33 a.m.