Triple
T3924194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jamestown Exposition |
E93232
|
entity |
| Predicate | hadVisitorType |
P1284
|
FINISHED |
| Object | domestic visitors |
—
|
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: domestic visitors | Statement: [Jamestown Exposition, hadVisitorType, domestic visitors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadVisitorType Context triple: [Jamestown Exposition, hadVisitorType, domestic visitors]
-
A.
hasVisitorType
chosen
Indicates the type or category of visitor associated with an entity (e.g., guest, customer, tourist, patient).
-
B.
hasTypeOfVisitorExperience
Indicates that an entity is associated with a particular category or kind of visitor experience it provides or involves.
-
C.
hasVisitation
Indicates that one entity visits, or is allowed or scheduled to visit, another entity or location.
-
D.
visitorStatus
Indicates the current state or condition of an entity in its role as a visitor (e.g., whether they are active, pending, past, or otherwise classified in their visit).
-
E.
hasVisitorServices
Indicates that an entity provides services or facilities specifically intended for visitors or guests.
- 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_69aed96bfa1081908f7b30f2c647dee6 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aeed7dacdc8190854ebc13db2d24bc |
completed | March 9, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69aee7609c4081908000ce12ae827c3f |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:23 p.m.