Triple
T10422621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marshfield, Plymouth Colony |
E245694
|
entity |
| Predicate | hadMeetinghouseBy |
P3175
|
FINISHED |
| Object | mid-17th century |
—
|
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: mid-17th century | Statement: [Marshfield, Plymouth Colony, hadMeetinghouseBy, mid-17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadMeetinghouseBy Context triple: [Marshfield, Plymouth Colony, hadMeetinghouseBy, mid-17th century]
-
A.
hadMeetingHouse
chosen
Indicates that an entity possessed or was associated with a specific meeting house as a place for gatherings or assemblies.
-
B.
hasHouse
Indicates that one entity possesses, owns, or is provided with a house in relation to another entity.
-
C.
hasGeneralHouse
Indicates that an entity possesses or is associated with a general-purpose house or primary residential building.
-
D.
hasHad
Indicates that an entity previously experienced, possessed, or was involved in something at some point in the past.
-
E.
houseVisited
Indicates that a particular house has been visited by a specified entity or at a specified time.
- 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_69d381bf3dc08190bf35a2643e4e8f22 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4ea2cd0788190b904ccdc251a9b7a |
completed | April 7, 2026, 11:27 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb9d3648190aaabed901f22a8c0 |
completed | April 7, 2026, 10:43 a.m. |
Created at: April 6, 2026, 12:12 p.m.