Triple
T6917273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delaware County, New York |
E160091
|
entity |
| Predicate | hasMajorActivity |
P40655
|
FINISHED |
| Object | hiking |
—
|
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: hiking | Statement: [Delaware County, New York, hasMajorActivity, hiking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorActivity Context triple: [Delaware County, New York, hasMajorActivity, hiking]
-
A.
hasSignificantActivity
Indicates that an entity exhibits a notable level or intensity of activity, performance, or operation relative to a defined threshold or context.
-
B.
hasActivityIn
Indicates that an entity engages in or performs a particular activity within a specified context, location, or domain.
-
C.
majorActivity
chosen
Indicates that the related entity performs, participates in, or is primarily associated with a main or most significant activity.
-
D.
hasMajorWork
Indicates that an entity (typically a person, creator, or organization) is associated with a significant or principal work they produced or are best known for.
-
E.
hasPrimaryActivities
Indicates that an entity is associated with one or more main activities that define its core functions or operations.
- 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_69c6883ab1008190a07129ff06f625d9 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6d9e034cc81908f1e8f31b055e119 |
completed | March 27, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b93d688190a297244ce81b67ac |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:26 p.m.