Triple
T29154066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vao |
E738988
|
entity |
| Predicate | ethnicTraditions |
P114983
|
FINISHED |
| Object | Kanak |
—
|
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: Kanak | Statement: [Vao, ethnicTraditions, Kanak]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ethnicTraditions Context triple: [Vao, ethnicTraditions, Kanak]
-
A.
culturalTradition
Indicates a relationship where certain practices, beliefs, or customs are recognized as part of a shared cultural heritage passed down within a group or society.
-
B.
languageTraditions
Indicates that there is a relationship between entities involving the customs, practices, and conventions associated with the use, preservation, or transmission of a particular language.
-
C.
cultOrTradition
Indicates that one entity is a cult or tradition associated with, practiced by, or characterizing another entity.
-
D.
heritageTradition
chosen
Indicates a relationship where a cultural practice, belief, or custom is passed down and maintained as part of a group’s inherited traditions.
-
E.
citesTradition
Indicates that one entity references, appeals to, or draws authority from a tradition associated with another entity.
- 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_69f07cb46f148190874eb8576a447567 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
Created at: April 28, 2026, 11:44 a.m.