Triple
T32922449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carthage Jail Visitors Center |
E842177
|
entity |
| Predicate | tourGuides |
P61809
|
FINISHED |
| Object | missionaries of The Church of Jesus Christ of Latter-day Saints |
—
|
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: missionaries of The Church of Jesus Christ of Latter-day Saints | Statement: [Carthage Jail Visitors Center, tourGuides, missionaries of The Church of Jesus Christ of Latter-day Saints]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tourGuides Context triple: [Carthage Jail Visitors Center, tourGuides, missionaries of The Church of Jesus Christ of Latter-day Saints]
-
A.
hasTouristGuidedTours
Indicates that an entity offers or provides guided tours specifically designed for tourists.
-
B.
inGuidebook
Indicates that something is included or featured as an entry within a guidebook.
-
C.
tourComponentOf
Indicates that something functions as a constituent part or segment of a larger tour.
-
D.
tourWith
chosen
Indicates that one entity accompanies another on a tour, sharing the same itinerary or guided experience.
-
E.
tourStaple
Indicates that something is a standard, frequently included element or highlight of a tour.
- 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_69f3494779388190a5d3e97f92278be2 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d0d7b7888190b93fe5556a28c470 |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe5f93c8190995c53dbbe380a32 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:19 a.m.