Triple
T33665664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William Bradford (frequent visitor and landholder) |
E862483
|
entity |
| Predicate | frequentVisitorTo |
P1097
|
FINISHED |
| Object | Marshfield |
—
|
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: Marshfield | Statement: [William Bradford (frequent visitor and landholder), frequentVisitorTo, Marshfield]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frequentVisitorTo Context triple: [William Bradford (frequent visitor and landholder), frequentVisitorTo, Marshfield]
-
A.
frequentlyVisitedBy
chosen
Indicates that an entity is regularly or often visited by another entity.
-
B.
oftenVisitedWith
Indicates that two entities are frequently visited together, typically during the same visit or trip.
-
C.
isMostFrequentlyVisitedRegionOf
Indicates that a region is the one visited most often by a particular entity compared to all other regions.
-
D.
visitorFrequency
Indicates how often a visitor comes to or interacts with a particular entity or location.
-
E.
reputedToBeVisitedBy
Indicates that an entity is commonly believed or reported to be visited by another entity, without necessarily confirming that the visits actually occur.
- 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_69f34984c4008190bb82f33a7819da64 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:42 a.m.