Triple
T8606270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shomrim neighborhood watch |
E203805
|
entity |
| Predicate | hasVolunteerBasis |
P5502
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Shomrim neighborhood watch, hasVolunteerBasis, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVolunteerBasis Context triple: [Shomrim neighborhood watch, hasVolunteerBasis, true]
-
A.
hasVolunteerBase
chosen
Indicates that an entity maintains or relies on a group of volunteers as a foundational support resource.
-
B.
hasVolunteerStatus
Indicates that an entity holds a particular volunteer-related status or role within a specified context.
-
C.
hasVolunteerProgram
Indicates that an organization or entity offers an organized program through which individuals can volunteer their time or services.
-
D.
volunteeredFor
Indicates that an entity willingly offered their time or services to support or participate in an activity, cause, or organization.
-
E.
hasVolunteerRescueSquad
Indicates that an entity is served or supported by a volunteer-based rescue or emergency response squad.
- 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_69ca832c23e4819095a9f3eea4a21828 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46eabe2c8190a2d13c353055a785 |
completed | March 31, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cc454eb2908190acf0e4336bc67e7b |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:25 p.m.