Triple
T36393491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Banlam people |
E896394
|
entity |
| Predicate | regionallyDominantGroupIn |
P65193
|
FINISHED |
| Object | southern Fujian |
—
|
NE NERFINISHED |
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: southern Fujian | Statement: [Banlam people, regionallyDominantGroupIn, southern Fujian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionallyDominantGroupIn Context triple: [Banlam people, regionallyDominantGroupIn, southern Fujian]
-
A.
ethnicGroupLocatedIn
Indicates that a particular ethnic group is present, resides, or is primarily associated with a specific geographic location or region.
-
B.
dominantEthnicGroups
chosen
Indicates that the specified ethnic groups hold primary demographic, cultural, or political prominence within a given region or population.
-
C.
ethnicGroupNamed
Indicates that an ethnic group bears or is identified by a particular name.
-
D.
ethnicGroupOn
Indicates that a particular ethnic group is present on, associated with, or resides in a specified place or entity.
-
E.
ethnicGroupBase
Indicates that one entity serves as the primary or foundational ethnic group from which another entity is derived, associated, or defined.
- 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_69f76e52e3108190becf70b090ae7bd6 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a0017dd31d08190aa5e9f72df83733a |
completed | May 10, 2026, 5:30 a.m. |
| PD | Predicate disambiguation | batch_6a0015a1deb88190b9cdaa60455b0a33 |
completed | May 10, 2026, 5:20 a.m. |
Created at: May 3, 2026, 4:10 p.m.