Triple
T29008231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pedetidae |
E736492
|
entity |
| Predicate | hasCommonNameForMembers |
P72013
|
FINISHED |
| Object | springhare |
—
|
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: springhare | Statement: [Pedetidae, hasCommonNameForMembers, springhare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommonNameForMembers Context triple: [Pedetidae, hasCommonNameForMembers, springhare]
-
A.
hasTypeMemberCommonName
chosen
Indicates that an entity has a commonly used or informal name associated with a specific type or category of its members.
-
B.
includesCommonName
Indicates that one entity contains or specifies a commonly used (non-scientific) name for another entity.
-
C.
hasTribeCommonName
Indicates that two entities are related by the commonly used (vernacular) name of a tribe.
-
D.
belongsToFamilyCommonName
Indicates that an entity is associated with, or classified under, a particular family-level common name.
-
E.
hasMembersWith
Indicates that a group or collection includes one or more specific members that satisfy a given condition or characteristic.
- 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_69f077eb81e88190ad9ff62cbb9f555e |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_6a0018cf6ebc8190aee6288788d0067e |
completed | May 10, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_6a001855e8588190a65840485473cf8b |
completed | May 10, 2026, 5:32 a.m. |
Created at: April 28, 2026, 9:40 a.m.