Triple
T36479530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Detroit City FC |
E898770
|
entity |
| Predicate | communityEngagementType |
P102091
|
FINISHED |
| Object | local outreach programs |
—
|
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: local outreach programs | Statement: [Detroit City FC, communityEngagementType, local outreach programs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: communityEngagementType Context triple: [Detroit City FC, communityEngagementType, local outreach programs]
-
A.
communityActivity
chosen
Indicates that an entity participates in, contributes to, or is involved with activities organized for or by a community.
-
B.
communityAspect
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.
communityOutcome
Indicates the result, impact, or consequence that an action, program, or event has on a community as a whole.
-
E.
communityMovement
Indicates a coordinated effort or shift undertaken collectively by members of a community toward a shared goal or change.
- 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_69f76e5a0e088190a2b6706aeb41723c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c477a4d481908f52e55b6688f60c |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:10 p.m.