Triple
T26364761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silat Betawi |
E660301
|
entity |
| Predicate | hasTrainingContext |
P69125
|
FINISHED |
| Object | Betawi neighborhoods |
—
|
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: Betawi neighborhoods | Statement: [Silat Betawi, hasTrainingContext, Betawi neighborhoods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrainingContext Context triple: [Silat Betawi, hasTrainingContext, Betawi neighborhoods]
-
A.
hasTrainingFor
Indicates that an entity has received or possesses training that prepares it for performing a specific task, role, or function.
-
B.
hasTrainingEnvironment
chosen
Indicates that an entity is associated with, or operates within, a specific environment or setting used for training or practice.
-
C.
hasTrained
Indicates that one entity has provided training or instruction to another entity.
-
D.
hasTrainingFunction
Indicates that one entity serves as a training function or mechanism for another entity.
-
E.
hasTrainingRole
Indicates that an entity holds or is assigned a specific role within a training or instructional context.
- 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_69ee8126d52c8190bc0b34337c2c9aa8 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
Created at: April 26, 2026, 10:54 p.m.