Triple
T26644774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lanier Middle School |
E668875
|
entity |
| Predicate | hasCommunityContext |
P196206
|
FINISHED |
| Object | urban school |
—
|
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: urban school | Statement: [Lanier Middle School, hasCommunityContext, urban school]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommunityContext Context triple: [Lanier Middle School, hasCommunityContext, urban school]
-
A.
hasCommunityIn
Indicates that a community is present, active, or established within a specified location, platform, or context.
-
B.
hasCommunityAspect
Indicates that something involves, reflects, or contributes to a shared community dimension, such as collective participation, interaction, or benefit.
-
C.
hasTargetCommunity
Indicates that something is specifically intended for, directed toward, or designed to serve a particular community or group.
-
D.
hasCommunityGroup
Indicates that an entity is associated with, or belongs to, a specific community group.
-
E.
hasCommunityArea
Indicates that an entity is associated with, located in, or belongs to a particular community area.
- F. None of above. chosen
Provenance (4 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_69ee9d00eb5481908d6c6d0ada2f0c9a |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69fe163a41a0819098403b470e327d29 |
completed | May 8, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fe1358db5c819092570814a37ef5bd |
completed | May 8, 2026, 4:46 p.m. |
| PDg | Predicate description generation | batch_69fe1639613c8190aaf1b4c8e2d861ba |
completed | May 8, 2026, 4:58 p.m. |
Created at: April 27, 2026, 2:30 a.m.