Triple
T25699693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jong Sumatra |
E644423
|
entity |
| Predicate | ethnicOrRegionalBase |
P159764
|
FINISHED |
| Object | Sumatran youth |
—
|
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: Sumatran youth | Statement: [Jong Sumatra, ethnicOrRegionalBase, Sumatran youth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ethnicOrRegionalBase Context triple: [Jong Sumatra, ethnicOrRegionalBase, Sumatran youth]
-
A.
ethnicRegionalBase
Indicates that an entity’s support, identity, or operations are primarily rooted in a specific ethnic group within a particular geographic region.
-
B.
hasEthnicOrRegionalOrigin
chosen
Indicates that an entity originates from, or is associated with, a particular ethnic group or geographic region.
-
C.
ethnicOrTribalBase
Indicates that something is founded on, derived from, or primarily organized around a particular ethnic or tribal group or identity.
-
D.
ethnicOrigin
Indicates the relationship where an entity is associated with a particular ethnic group or ancestry.
-
E.
ethnoLinguisticRegionOf
Indicates that a region is defined or characterized by the shared ethnic and linguistic identity of the group associated with it.
- 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_69e77e82c9bc8190893090b2f6c64f1d |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f62d89b89c8190afb372a8172111e7 |
completed | May 2, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69f62c1379f08190836c3e02b0c892df |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 21, 2026, 8:43 p.m.