Triple
T1573177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Pleasant |
E33586
|
entity |
| Predicate | ethnicCommunities |
P12220
|
FINISHED |
| Object | Latino 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: Latino community | Statement: [Mount Pleasant, ethnicCommunities, Latino community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ethnicCommunities Context triple: [Mount Pleasant, ethnicCommunities, Latino community]
-
A.
involvedEthnicGroup
chosen
Indicates that a particular ethnic group participates in, is affected by, or is otherwise associated with the referenced event, situation, or entity.
-
B.
otherEthnicGroup
Indicates that one entity belongs to a different ethnic group than the other entity.
-
C.
ethnicGroupResearched
Indicates that a particular ethnic group is the subject or focus of a research activity or study conducted by an entity.
-
D.
indigenousCommunity
Indicates that an entity is an indigenous community, i.e., a group with historical, cultural, and ancestral ties to a specific territory predating external or colonial societies.
-
E.
ethnicSubdivisionOf
Indicates that one ethnic group is a constituent subgroup or branch within a larger, overarching ethnic group.
- 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_69a885f11b048190935025a035302715 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a96083e7308190abbf025fe8e43abb |
completed | March 5, 2026, 10:52 a.m. |
| PD | Predicate disambiguation | batch_69a907ba63c88190b60c14dec8d1e40f |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:27 p.m.