Triple
T32871554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jonathan Small |
E840805
|
entity |
| Predicate | losesLegIn |
P175537
|
FINISHED |
| Object | crocodile attack |
—
|
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: crocodile attack | Statement: [Jonathan Small, losesLegIn, crocodile attack]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: losesLegIn Context triple: [Jonathan Small, losesLegIn, crocodile attack]
-
A.
domesticLegIn
Indicates that a particular segment or leg of a journey or itinerary occurs within the domestic boundaries of a specified country or region.
-
B.
legs
Indicates that an entity possesses legs, specifying the presence or number of leg-like appendages associated with it.
-
C.
originalLegFinish
Indicates that an entity represents the final segment or completion state of an original leg in a multi-leg process or journey.
-
D.
firstLeg
Indicates that one entity represents the initial segment or starting portion of a multi-part journey, sequence, or process involving another entity.
-
E.
includedLegs
Indicates that certain legs (segments of a journey or process) are part of, or contained within, a larger composite route or sequence.
- 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_69f349436ee88190b72ee12d0f3f508e |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d210fc80819091ed8961aa2cddfb |
completed | May 3, 2026, 4:41 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe45554819089cbbd538d992132 |
completed | May 3, 2026, 4:32 a.m. |
| PDg | Predicate description generation | batch_69f6d16b79dc8190ab0d4657f2ef9a5b |
completed | May 3, 2026, 4:39 a.m. |
Created at: May 1, 2026, 1:17 a.m.