Triple
T10895146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Puvungna |
E257288
|
entity |
| Predicate | hasOngoingUse |
P15255
|
FINISHED |
| Object | contemporary Indigenous ceremonies |
—
|
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: contemporary Indigenous ceremonies | Statement: [Puvungna, hasOngoingUse, contemporary Indigenous ceremonies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOngoingUse Context triple: [Puvungna, hasOngoingUse, contemporary Indigenous ceremonies]
-
A.
hasOngoing
Indicates that one entity is currently engaged in, experiencing, or maintaining an activity, state, or process that has not yet concluded.
-
B.
hasOnlineActivity
Indicates that an entity engages in or possesses some form of activity or presence on the internet or digital platforms.
-
C.
isOngoing
Indicates that an action, process, or state is currently in progress and has not yet been completed or concluded.
-
D.
isInUse
chosen
Indicates that an entity is currently being utilized or actively engaged in its intended function or operation.
-
E.
usageStatus
Indicates the current state or condition of how something is being used, such as whether it is active, inactive, available, or in use.
- 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_69d6aa8550c8819095508a2ed9acf3db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d75d0153408190bcba2d9b03d78804 |
completed | April 9, 2026, 8:02 a.m. |
| PD | Predicate disambiguation | batch_69d70d3943c881908895397eccc3e415 |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:21 p.m.