Triple
T30190689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nadine Groot |
E767471
|
entity |
| Predicate | journeyCharacteristic |
P87607
|
FINISHED |
| Object | perilous cattle drive |
—
|
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: perilous cattle drive | Statement: [Nadine Groot, journeyCharacteristic, perilous cattle drive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: journeyCharacteristic Context triple: [Nadine Groot, journeyCharacteristic, perilous cattle drive]
-
A.
travelCharacteristic
chosen
Indicates a quality, feature, or attribute that characterizes how travel or movement is conducted or experienced.
-
B.
journey
Indicates that an entity travels or moves from one place or state to another, typically over a period of time or distance.
-
C.
tourismCharacteristic
Indicates that something has a specific feature, quality, or attribute relevant to tourism, such as what makes a place, service, or activity notable or suitable for tourists.
-
D.
journeyDestination
Indicates that one entity serves as the endpoint or intended destination of another entity’s journey or travel.
-
E.
journeyFrom
Indicates that an entity undertakes or originates a journey starting from a specified location or source.
- 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_69f2247cc3d88190811dec3face94bf5 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67f8393948190aa6fc6acea2e7d00 |
completed | May 2, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 7:28 p.m.