Triple
T33479563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luke |
E857431
|
entity |
| Predicate | purposeOfTrip |
P102055
|
FINISHED |
| Object | memorial hiking trip for Rob |
—
|
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: memorial hiking trip for Rob | Statement: [Luke, purposeOfTrip, memorial hiking trip for Rob]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: purposeOfTrip Context triple: [Luke, purposeOfTrip, memorial hiking trip for Rob]
-
A.
journeyPurpose
chosen
Indicates the reason or intended goal motivating an entity’s journey or trip.
-
B.
typicalJourneyPurpose
Indicates the usual or most common reason or objective for which an entity undertakes a journey.
-
C.
bookingPurpose
Indicates the reason or intended use for which a booking or reservation is made.
-
D.
transportPurpose
Indicates that one entity is transported or moved specifically for the purpose, goal, or intended use denoted by another entity.
-
E.
sunJourneyPurpose
Indicates the purpose or intended goal behind a sun-related journey or movement.
- 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_69f3497472508190b300ebd3fd402367 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:38 a.m.