Triple
T38570784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Chatfield High School |
E929263
|
entity |
| Predicate | communitySignificance |
P47277
|
FINISHED |
| Object | recognized |
—
|
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: recognized | Statement: [Old Chatfield High School, communitySignificance, recognized]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: communitySignificance Context triple: [Old Chatfield High School, communitySignificance, recognized]
-
A.
community
Indicates a relationship where individuals or groups are connected by shared location, interests, or identity, forming a collective social unit.
-
B.
communityAspect
chosen
Indicates that something pertains to, reflects, or influences the communal or social dimension of a group or community.
-
C.
communityType
Indicates the classification or category of community to which an entity belongs (e.g., urban, rural, online, professional).
-
D.
communityUsage
Indicates how something is used, adopted, or engaged with by a particular community or group of people.
-
E.
communityAddressed
Indicates that a communication, action, or initiative is specifically directed toward or intended for a particular community as its audience or target.
- 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_69f76ebd2248819083978362d81fa35e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.