Triple
T32707669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pteranodon |
E836316
|
entity |
| Predicate | likelyAte |
P175027
|
FINISHED |
| Object | fish |
—
|
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: fish | Statement: [Pteranodon, likelyAte, fish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: likelyAte Context triple: [Pteranodon, likelyAte, fish]
-
A.
eatenAs
Indicates that one entity is consumed or used as food by another entity.
-
B.
eatenOnOccasion
Indicates that one entity is consumed or eaten by another only at certain times or under specific circumstances, rather than regularly or habitually.
-
C.
likelyIndicates
Indicates that one fact, observation, or condition serves as probabilistic evidence suggesting, but not guaranteeing, the presence or truth of another.
-
D.
likesFood
Indicates that an entity has a positive preference for or enjoyment of a particular food.
-
E.
likelyStatus
Indicates the probable or expected state or condition of an entity based on available information or inference.
- F. None of above. chosen
Provenance (4 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_69f3493446148190819541f3ffe79975 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6cd9bae8c8190b528641499162a75 |
completed | May 3, 2026, 4:22 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1470808190b70cdfd7a6395670 |
completed | May 3, 2026, 4:16 a.m. |
| PDg | Predicate description generation | batch_69f6cd119cac8190a0b3ebe8b9c742c2 |
completed | May 3, 2026, 4:20 a.m. |
Created at: May 1, 2026, 1:10 a.m.