Triple
T18551565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panthera onca |
E453390
|
entity |
| Predicate | biteAdaptation |
P128829
|
FINISHED |
| Object | crushing skulls of prey |
—
|
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: crushing skulls of prey | Statement: [Panthera onca, biteAdaptation, crushing skulls of prey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: biteAdaptation Context triple: [Panthera onca, biteAdaptation, crushing skulls of prey]
-
A.
biteTime
Indicates the time at which a biting action occurs or is scheduled to occur between entities.
-
B.
toothAdaptation
chosen
Indicates how an organism’s teeth are structurally or functionally modified in response to its diet, environment, or evolutionary pressures.
-
C.
biteLocationPreference
Indicates a tendency or pattern regarding where on a target an entity prefers to bite.
-
D.
isAdaptation
Indicates that one work is derived from, based on, or reinterprets the content of another work.
-
E.
bites
Indicates that one entity uses its teeth to grip, wound, or cut into 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_69d8d388b0c881908e610a1c45b52640 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e538019a74819099dbd255fb21fa95 |
completed | April 19, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69e469e274a48190a570b25cfef4d890 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:38 a.m.