Triple
T11840584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Urban Hiligaynon |
E281638
|
entity |
| Predicate | hasSpeechCommunityType |
P3292
|
FINISHED |
| Object | urban speech 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: urban speech community | Statement: [Urban Hiligaynon, hasSpeechCommunityType, urban speech community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpeechCommunityType Context triple: [Urban Hiligaynon, hasSpeechCommunityType, urban speech community]
-
A.
hasLanguageCommunity
Indicates that an entity is associated with or serves a particular language community.
-
B.
hasCommunityType
chosen
Indicates that an entity is associated with or classified under a particular type or category of community.
-
C.
spokenByCommunity
Indicates that a language, dialect, or expression is used or articulated collectively by a particular community.
-
D.
isSpokenAround
Indicates that something (such as a language, phrase, or expression) is commonly spoken in the vicinity of, or within the general area surrounding, a particular place or entity.
-
E.
isSpokenOn
Indicates that a particular language, phrase, or utterance is used or occurs during a specified time, event, or occasion.
- 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_69d6ab276f8c8190b1966a0ef11349ac |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a658f918819092c2db05fe2ab0ce |
completed | April 10, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69d8a254a57481908a1e6ad97919c416 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:43 p.m.