Triple
T25436921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ursus ingressus |
E637400
|
entity |
| Predicate | hasSkeletalElement |
P7379
|
FINISHED |
| Object | skull fossils |
—
|
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: skull fossils | Statement: [Ursus ingressus, hasSkeletalElement, skull fossils]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSkeletalElement Context triple: [Ursus ingressus, hasSkeletalElement, skull fossils]
-
A.
hasSkeleton
Indicates that an entity possesses a skeleton as part of its bodily structure.
-
B.
haveSkeletonComposedOf
Indicates that an entity’s skeleton is made up of, or structurally formed from, a specified material or component.
-
C.
skeletonCompleteness
Indicates the degree to which an entity’s skeleton is present, intact, or fully preserved in relation to its expected complete form.
-
D.
skeletonLacks
Indicates that an entity’s skeleton does not possess or is missing a specified bone, feature, or structural component.
-
E.
skeletonFeature
chosen
Indicates that one entity is a structural or anatomical skeletal feature or component of another entity.
- 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_69e75db6c97081908178383fa632b193 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f6e36f3c819084cb3f9d2ecec135 |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f4683b34748190818428489a226124 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 2 p.m.