Triple
T24945695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kulin languages |
E624179
|
entity |
| Predicate | haveRevitalizationEfforts |
P4089
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Kulin languages, haveRevitalizationEfforts, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haveRevitalizationEfforts Context triple: [Kulin languages, haveRevitalizationEfforts, yes]
-
A.
revitalizationEffort
chosen
Indicates efforts or actions undertaken to restore, renew, or improve the condition, vitality, or functionality of something.
-
B.
revitalizationEffortIn
Indicates that a revitalization effort or improvement initiative is being carried out within a specified location or area.
-
C.
revitalizationNeed
Indicates that an entity requires renewal, restoration, or significant improvement to regain vitality, functionality, or effectiveness.
-
D.
goalOfRevitalization
Indicates an effort or initiative aimed at restoring, renewing, or strengthening something that has declined or weakened.
-
E.
revitalizationCountry
Indicates the country in which a revitalization effort, project, or process takes place or is targeted.
- 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_69e2ff22e4c48190a0444b5a044f14e8 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d77f6e88190a4643ab2cbef567b |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 5:54 a.m.