Triple
T12777637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huntington Park |
E305417
|
entity |
| Predicate | secondaryLanguageSpokenAtHome |
P9103
|
FINISHED |
| Object | English |
—
|
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: English | Statement: [Huntington Park, secondaryLanguageSpokenAtHome, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryLanguageSpokenAtHome Context triple: [Huntington Park, secondaryLanguageSpokenAtHome, English]
-
A.
parentLanguage
Indicates that one language is the ancestral or source language from which another language is derived or historically developed.
-
B.
hasSecondaryLanguage
chosen
Indicates that an entity possesses or uses a secondary language in addition to its primary language.
-
C.
nativeLanguage
Indicates the language that a person or entity originally learned and uses as their primary or first language.
-
D.
hasSecondaryLanguageNearby
Indicates that an entity has at least one secondary language present or used in its immediate vicinity or surrounding context.
-
E.
laterLanguageDominant
Indicates that one language becomes the dominant or primary language for an entity at a later point in time, after another language previously held that role.
- 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_69d7bdf2b43c819098ae5aa68e61ea58 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e595e008190b42dff3012d17d66 |
completed | April 10, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69d9640ba0688190973e4e7ec8d4a8e0 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:29 p.m.