Triple
T11718561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaurna language |
E278564
|
entity |
| Predicate | hasRevivalGoal |
P60880
|
FINISHED |
| Object | intergenerational transmission |
—
|
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: intergenerational transmission | Statement: [Kaurna language, hasRevivalGoal, intergenerational transmission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRevivalGoal Context triple: [Kaurna language, hasRevivalGoal, intergenerational transmission]
-
A.
hasRevivalsIn
Indicates that something has been brought back, renewed, or reintroduced in specific times, places, or contexts.
-
B.
isFrequentlyRevived
Indicates that an entity is brought back, restored, or reintroduced many times over a period.
-
C.
hasRevitalizationMovement
chosen
Indicates that there exists an organized effort or movement aimed at renewing, restoring, or reinvigorating the subject entity.
-
D.
hasMaintenanceGoal
Indicates that an entity is associated with a specific objective or target related to its upkeep, repair, or ongoing maintenance activities.
-
E.
revivedAs
Indicates that an entity, after having ceased to exist or function in its original form, comes back into existence or operation in a new or restored form.
- 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_69d6aaff2ce88190b4a1e4b341ad5377 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4c26e4c8190ae30d906b4fd4221 |
completed | April 10, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69d88a7d483081909c2a101087515d74 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:40 p.m.