Triple
T1408144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ride with Norman Reedus |
E31742
|
entity |
| Predicate | hasSeasonType |
P26586
|
FINISHED |
| Object | episodic travel adventures |
—
|
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: episodic travel adventures | Statement: [Ride with Norman Reedus, hasSeasonType, episodic travel adventures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeasonType Context triple: [Ride with Norman Reedus, hasSeasonType, episodic travel adventures]
-
A.
hasSeason
Indicates that an entity possesses, occurs during, or is associated with a particular season or set of seasons.
-
B.
hasSeasonalStatus
Indicates that an entity’s status, availability, or condition varies according to a particular season or time of year.
-
C.
hasSeasonalPattern
Indicates that the occurrence, intensity, or characteristics of something regularly vary according to a recurring seasonal cycle.
-
D.
hasImportantSeason
Indicates that an entity experiences a particular season or time period that is especially significant or notable for it.
-
E.
hasMonthType
Indicates that something is associated with, classified by, or characterized as a particular type or category of month.
- 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_69a49918e1f88190ba610f9dc8114578 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c3bf7f0c8190aee96818de6ff4a5 |
completed | March 1, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69a4bf048b648190ab77d9b45cb4855f |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4bf8158ac8190b8360ecccc2980bc |
completed | March 1, 2026, 10:36 p.m. |
Created at: March 1, 2026, 7:59 p.m.