Triple
T23739665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the Crood family |
E586639
|
entity |
| Predicate | facesEvent |
P17155
|
FINISHED |
| Object | destruction of their cave |
—
|
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: destruction of their cave | Statement: [the Crood family, facesEvent, destruction of their cave]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: facesEvent Context triple: [the Crood family, facesEvent, destruction of their cave]
-
A.
facedEvent
chosen
Indicates that an entity directly encountered, experienced, or dealt with a particular event.
-
B.
facedChange
Indicates that an entity has encountered and had to deal with a modification, challenge, or transition affecting its prior state or circumstances.
-
C.
facesChallenge
Indicates that an entity is confronted with a difficulty, obstacle, or demanding situation that must be dealt with or overcome.
-
D.
facesBuilding
Indicates that one building is oriented toward and directly faces another building.
-
E.
isFaceOn
Indicates that one surface or side of an object is oriented directly toward, or aligned to face, another object or reference direction.
- 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_69e24908efb08190bf755c3a9b91f222 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bad5209081909c44380816bec377 |
completed | April 29, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69f155f012808190a4b1cbc155558ade |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 7:11 p.m.