Triple
T28542666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | W. P. Inman |
E722338
|
entity |
| Predicate | journeyMotivation |
P102055
|
FINISHED |
| Object | returning to Ada Monroe |
—
|
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: returning to Ada Monroe | Statement: [W. P. Inman, journeyMotivation, returning to Ada Monroe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: journeyMotivation Context triple: [W. P. Inman, journeyMotivation, returning to Ada Monroe]
-
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.
sunJourneyPurpose
Indicates the purpose or intended goal behind a sun-related journey or movement.
-
D.
tourismMotivation
Indicates the reasons or driving factors that motivate an entity (typically a person) to engage in tourism or travel activities.
-
E.
journey
Indicates that an entity travels or moves from one place or state to another, typically over a period of time or distance.
- 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_69f01a5e42348190b1ffbca26e739c84 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f6500b2f1881908d21a0cbc7877ebf |
completed | May 2, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 3:36 a.m.