Triple
T30341031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Overmountain Men |
E771752
|
entity |
| Predicate | gatheringPoint |
P16368
|
FINISHED |
| Object | Sycamore Shoals |
—
|
NE NERFINISHED |
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: Sycamore Shoals | Statement: [Overmountain Men, gatheringPoint, Sycamore Shoals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gatheringPoint Context triple: [Overmountain Men, gatheringPoint, Sycamore Shoals]
-
A.
gatheringPlace
chosen
Indicates a location where entities come together or assemble, typically for a shared activity, purpose, or event.
-
B.
traditionalMeetingPlace
Indicates that a location is customarily used as a gathering spot for meetings or social interactions according to established tradition.
-
C.
gathering
Indicates that one or more entities are coming together or being brought together into a group at a particular time or place.
-
D.
meetingPlaceOf
Indicates the location where a particular meeting or gathering takes place or is held for the referenced entities.
-
E.
collectionPoint
Indicates a location or entity designated as the place where items are gathered, received, or collected.
- 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_69f2248b9a208190bc3e6804acd5afd6 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68202f0fc8190b6ad7101515ae10f |
completed | May 2, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69f67603526c81908295a1ece8727c66 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:55 p.m.