Triple
T2664042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Selma Interpretive Center |
E54788
|
entity |
| Predicate | hasTypeOfTour |
P7952
|
FINISHED |
| Object | self-guided tours |
—
|
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: self-guided tours | Statement: [Selma Interpretive Center, hasTypeOfTour, self-guided tours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfTour Context triple: [Selma Interpretive Center, hasTypeOfTour, self-guided tours]
-
A.
hasTour
chosen
Indicates that an entity offers, includes, or is associated with a tour experience or guided visit.
-
B.
hasResortType
Indicates that an entity (such as a resort or accommodation) is associated with a specific category or type of resort (e.g., beach resort, ski resort, spa resort).
-
C.
hasAttractionType
Indicates that one entity is associated with a specific kind or category of attraction (e.g., tourist, cultural, natural).
-
D.
hasTouristRoute
Indicates that a location or site is connected to or included in a designated tourist route or itinerary.
-
E.
hasTourismFunction
Indicates that an entity serves a role or purpose related to tourism, such as attracting, accommodating, or providing services to tourists.
- 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_69ab49e028948190b97e01d73548b1d9 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd96dba44819085c3e651afba7806 |
completed | March 7, 2026, 7:53 a.m. |
| PD | Predicate disambiguation | batch_69abd81768748190bd965f367cf6ef37 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:54 p.m.