Triple
T22826230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weequahic High School |
E565666
|
entity |
| Predicate | hasCommunityTies |
P136131
|
FINISHED |
| Object | deep ties to local community |
—
|
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: deep ties to local community | Statement: [Weequahic High School, hasCommunityTies, deep ties to local community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommunityTies Context triple: [Weequahic High School, hasCommunityTies, deep ties to local community]
-
A.
hasCommunityLinks
chosen
Indicates that an entity maintains relationships, partnerships, or active connections with one or more communities.
-
B.
hasStrongTiesTo
Indicates a close, influential, and enduring relationship or connection exists between the referenced entities.
-
C.
hasCommunityLink
Indicates that there exists an established connection or association between an entity and a community.
-
D.
hasCommunityIn
Indicates that a community is present, active, or established within a specified location, platform, or context.
-
E.
hasIndustryTies
Indicates that an entity maintains professional, financial, or organizational connections with a particular industry or sector.
- 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_69e24585ab1c81909b2b5065d15805d5 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17e2832b8819091c1dfd2cd598b90 |
completed | April 29, 2026, 3:42 a.m. |
| PD | Predicate disambiguation | batch_69eed2d117088190acbfe130d84f8627 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:34 p.m.