Triple
T33664208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scituate School District |
E862438
|
entity |
| Predicate | hasVillageInDistrict |
P4011
|
FINISHED |
| Object | Clayville |
—
|
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: Clayville | Statement: [Scituate School District, hasVillageInDistrict, Clayville]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVillageInDistrict Context triple: [Scituate School District, hasVillageInDistrict, Clayville]
-
A.
isVillageDistrictOf
Indicates that one administrative unit is a village-level district that belongs to or is governed by a larger territorial entity.
-
B.
hasVillage
chosen
Indicates that an entity possesses, contains, or is associated with a village.
-
C.
hasVillageCommunity
Indicates that an entity possesses, is associated with, or includes a village-level community as part of its structure or domain.
-
D.
isRuralDistrictOf
Indicates that one administrative area is a rural district that belongs to or is governed as part of another, typically larger, administrative unit.
-
E.
hasVillageAtExit
Indicates that a village is located at or directly adjacent to an exit (such as a road, highway, or route exit).
- 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_69fd2839880c819099a7a89783f2270e |
completed | May 8, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69fd23dc5da48190ae8ba08947d34956 |
completed | May 7, 2026, 11:44 p.m. |
Created at: May 1, 2026, 1:42 a.m.