Triple
T7391756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RiverFest (Eden, North Carolina) |
E170516
|
entity |
| Predicate | typicalLocationFeature |
P46334
|
FINISHED |
| Object | near rivers |
—
|
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: near rivers | Statement: [RiverFest (Eden, North Carolina), typicalLocationFeature, near rivers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalLocationFeature Context triple: [RiverFest (Eden, North Carolina), typicalLocationFeature, near rivers]
-
A.
notableLocationFeature
chosen
Indicates that a location is characterized or distinguished by a particular notable physical or contextual feature.
-
B.
typicalUseLocation
Indicates the usual or most common location where an entity is used or operates.
-
C.
featuresLocation
Indicates that something is characterized by or includes a specific location as one of its notable attributes.
-
D.
notableLocationFeatured
Indicates that a particular location is prominently highlighted or showcased in relation to the subject.
-
E.
typicalOnsetLocation
Indicates the anatomical location where a condition, symptom, or process most commonly begins or first appears.
- 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_69c68a5e2c9081909e713ce866e0060a |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f22318108190a4dde257fe9e947f |
completed | March 27, 2026, 9:09 p.m. |
| PD | Predicate disambiguation | batch_69c6f0309cc88190b55d278969400294 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:09 p.m.