Triple
T33310133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tsavo man-eaters |
E852849
|
entity |
| Predicate | possibleCauseOfManEating |
P146054
|
FINISHED |
| Object | dental disease |
—
|
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: dental disease | Statement: [Tsavo man-eaters, possibleCauseOfManEating, dental disease]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: possibleCauseOfManEating Context triple: [Tsavo man-eaters, possibleCauseOfManEating, dental disease]
-
A.
isEatenIn
Indicates that one entity (typically food) is consumed within the context, location, or occasion specified by another entity.
-
B.
possibleCauseOf
chosen
Indicates that one entity is a potential, but not certain, cause or contributing factor to another entity or outcome.
-
C.
eatenAndResurrectedIn
Indicates that an entity was eaten in a particular place or context and later brought back to life or restored there.
-
D.
naturalOrHumanCause
Indicates that something results from either natural processes or human activities as its cause.
-
E.
largelyConsumedBy
Indicates that something is mostly or predominantly eaten or used up by a particular consumer or group.
- 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_69f349679fd8819093b9b40e989440e3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
Created at: May 1, 2026, 1:33 a.m.