Triple
T5632990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vombatus ursinus |
E147876
|
entity |
| Predicate | diggingAdaptation |
P2375
|
FINISHED |
| Object | strong claws |
—
|
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: strong claws | Statement: [Vombatus ursinus, diggingAdaptation, strong claws]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: diggingAdaptation Context triple: [Vombatus ursinus, diggingAdaptation, strong claws]
-
A.
adaptation
Indicates a relationship where one entity changes or is modified to better suit, function within, or correspond to another entity or context.
-
B.
adaptationDetail
Indicates that additional information is provided about how something has been adapted or modified from its original form.
-
C.
adaptationType
chosen
Indicates the specific kind or category of adaptation that relates one entity to another or to a particular context.
-
D.
excavated
Indicates that one entity has dug out, uncovered, or removed earth or material from another entity, typically to reveal or extract what lies beneath.
-
E.
isAdaptation
Indicates that one work is derived from, based on, or reinterprets the content of another work.
- 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_69c00907bc8881909ed760d3ed73ef35 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0225ff3248190b93c9f5887553fd4 |
completed | March 22, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69c01b1f12ec8190b4b9d9ee31cabe19 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:41 p.m.