Triple
T6845863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kennesaw Mountain |
E157891
|
entity |
| Predicate | hasShuttleService |
P3493
|
FINISHED |
| Object | seasonal summit shuttle |
—
|
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: seasonal summit shuttle | Statement: [Kennesaw Mountain, hasShuttleService, seasonal summit shuttle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasShuttleService Context triple: [Kennesaw Mountain, hasShuttleService, seasonal summit shuttle]
-
A.
hasShuttleLine
chosen
Indicates that there is a shuttle service or route operating between the related entities.
-
B.
hasPassengerServicesTo
Indicates that a transportation provider operates passenger services connecting one location or entity to another.
-
C.
hasBusServices
Indicates that one location or entity is served by bus routes or bus transportation provided by another.
-
D.
hasFerryService
Indicates that there is an operational ferry connection or transport service available between the related locations or entities.
-
E.
transportationServedBy
Indicates that a transportation facility, route, or area is provided service or coverage by a specific transportation provider or mode.
- 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_69c6882ed4c081909dc465a7cf8838be |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d7cbe4488190b41ddf953f12f55f |
completed | March 27, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69c6d09f90648190bc0a462c7d59de1b |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:20 p.m.