Triple
T15610947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hoosac School |
E375286
|
entity |
| Predicate | hasCommunityValue |
P66257
|
FINISHED |
| Object | close-knit relationships |
—
|
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: close-knit relationships | Statement: [Hoosac School, hasCommunityValue, close-knit relationships]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommunityValue Context triple: [Hoosac School, hasCommunityValue, close-knit relationships]
-
A.
hasCommunityIn
Indicates that a community is present, active, or established within a specified location, platform, or context.
-
B.
hasCommunityGroup
Indicates that an entity is associated with, or belongs to, a specific community group.
-
C.
hasCommunityAspect
chosen
Indicates that something involves, reflects, or contributes to a shared community dimension, such as collective participation, interaction, or benefit.
-
D.
hasCommunityAttribute
Indicates that a community possesses or is characterized by a specific attribute or property.
-
E.
hasCommunityArea
Indicates that an entity is associated with, located in, or belongs to a particular community area.
- 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_69d85ccf2794819096cda4cbcb02d478 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e8148a0819087d6d69cc84487ca |
completed | April 16, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69deda844af081909e658ebc9d9b403d |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:13 a.m.