Triple
T35484549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hopedale Council Chamber |
E1025556
|
entity |
| Predicate | servesPeople |
P201627
|
FINISHED |
| Object | Inuit |
—
|
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: Inuit | Statement: [Hopedale Council Chamber, servesPeople, Inuit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesPeople Context triple: [Hopedale Council Chamber, servesPeople, Inuit]
-
A.
servesType
Indicates that one entity provides, offers, or is used to deliver a particular type, category, or kind of thing or service.
-
B.
isTypicallyServedFor
Indicates that one item is most commonly or customarily served as a meal or course for the other (e.g., a dish typically served for breakfast, lunch, or dinner).
-
C.
servesHouse
Indicates that an entity provides service, support, or functions on behalf of a particular house or household.
-
D.
servesFamily
Indicates that an entity provides food, services, or accommodations suitable for families, typically welcoming and catering to family groups.
-
E.
intendedToServe
Indicates that one entity was designed, planned, or purposed specifically to benefit, assist, or fulfill the needs of another entity.
- F. None of above. chosen
Provenance (4 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_69f76dfbcdd881908c7b0b6bc502252b |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a000efe971081909de03f875a7ad6cc |
completed | May 10, 2026, 4:52 a.m. |
| PD | Predicate disambiguation | batch_6a000c4ffe788190a5757af60aadd9f3 |
completed | May 10, 2026, 4:40 a.m. |
| PDg | Predicate description generation | batch_6a000efdbe948190b4bfa9871aa1a7ee |
completed | May 10, 2026, 4:52 a.m. |
Created at: May 3, 2026, 4:04 p.m.