Triple
T3801056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Thousand-Mile Walk to the Gulf |
E91687
|
entity |
| Predicate | describesActivity |
P8834
|
FINISHED |
| Object | long-distance walking |
—
|
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: long-distance walking | Statement: [A Thousand-Mile Walk to the Gulf, describesActivity, long-distance walking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describesActivity Context triple: [A Thousand-Mile Walk to the Gulf, describesActivity, long-distance walking]
-
A.
activityType
chosen
Indicates the specific kind or category of action or event that an entity is engaged in or associated with.
-
B.
typicalActivity
Indicates that an entity is commonly or characteristically engaged in a particular activity.
-
C.
settingOfActivities
Indicates that a particular place or context serves as the environment in which certain activities occur or are carried out.
-
D.
eventDescription
Indicates that a textual summary or explanation is provided describing what happens in the event.
-
E.
coordinatesActivitiesOf
Indicates that one entity organizes, aligns, or manages the activities of another entity or group of entities so they work together effectively.
- 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_69aed96354f48190a768966d6bd19b04 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aee8db8a288190afd1e3b9dcf02e97 |
completed | March 9, 2026, 3:35 p.m. |
| PD | Predicate disambiguation | batch_69aee7461abc8190945716f4b93e1a18 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:15 p.m.