Triple
T7567005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Fernando, California |
E178940
|
entity |
| Predicate | hasPredominantCommunity |
P2321
|
FINISHED |
| Object | Latino |
—
|
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 | Statement: [San Fernando, California, hasPredominantCommunity, Latino]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPredominantCommunity Context triple: [San Fernando, California, hasPredominantCommunity, Latino]
-
A.
hasMajorCommunity
chosen
Indicates that an entity possesses a primary or significantly large community associated with it.
-
B.
dominantCommunity
Indicates that one community holds a prevailing or controlling influence, status, or presence over others within a given context.
-
C.
hasCommunityArea
Indicates that an entity is associated with, located in, or belongs to a particular community area.
-
D.
hasCommunityIn
Indicates that a community is present, active, or established within a specified location, platform, or context.
-
E.
northernPartPredominantCommunity
Indicates that the predominant community being referred to is located in the northern part of a larger area or region.
- 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_69c69f2f80288190b95cceb4da92ab2b |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f91c717881909c88901cc3b101c7 |
completed | March 27, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69c6f4dc485c819080da13e3b7f4f08f |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:50 p.m.