Triple
T59565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chamorro |
E1180
|
entity |
| Predicate | hasLanguageRevitalizationEfforts |
P4252
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Chamorro, hasLanguageRevitalizationEfforts, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLanguageRevitalizationEfforts Context triple: [Chamorro, hasLanguageRevitalizationEfforts, true]
-
A.
hasApproximateNativeSpeakers
Indicates that an entity is associated with an estimated or approximate number of people who speak it as their native language.
-
B.
historicallySpokenIn
Indicates that a language was used for spoken communication in a particular place or region during a past historical period.
-
C.
hasLanguageOfOrigin
Indicates that one entity has its origin or source in the language specified by another entity.
-
D.
isWidelySpokenIn
Indicates that a language is spoken by a large portion of the population across many regions or communities within a specified area.
-
E.
isOfficialMinorityLanguageIn
Indicates that a language has formal, legally recognized minority-language status within a specified political or geographic entity.
- F. None of above. chosen
Provenance (4 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_69a24a552ef88190a0df287d68c65cba |
completed | Feb. 28, 2026, 1:52 a.m. |
| NER | Named-entity recognition | batch_69a250e401288190ba12322c9c5f07c9 |
completed | Feb. 28, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69a24e9f40908190a2f4a2111469b733 |
completed | Feb. 28, 2026, 2:10 a.m. |
| PDg | Predicate description generation | batch_69a250e2a80881909e5a653260e6f8e0 |
completed | Feb. 28, 2026, 2:20 a.m. |
Created at: Feb. 28, 2026, 1:55 a.m.