Triple
T31354194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | pca |
E799680
|
entity |
| Predicate | hasPopolocaVariety |
P196662
|
FINISHED |
| Object | Popoloca language |
—
|
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: Popoloca language | Statement: [pca, hasPopolocaVariety, Popoloca language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPopolocaVariety Context triple: [pca, hasPopolocaVariety, Popoloca language]
-
A.
isRepresentativeVarietyOf
Indicates that one entity serves as a typical or standard example representing the broader characteristics of another entity or group.
-
B.
isInlandVarietyOf
Indicates that one entity is a variety or subtype of another that occurs specifically in inland (non-coastal) areas.
-
C.
usesNativeVarieties
Indicates that an entity employs or incorporates locally adapted or indigenous varieties (such as plant, animal, or material types) in its activities or processes.
-
D.
hasLowerVariety
Indicates that one entity possesses a smaller or less diverse range of types, forms, or instances compared to another entity.
-
E.
isPrimaryVarietyOf
Indicates that one variety is the main or principal form of another related variety or 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_69f224e5e9bc8190a16339328897c4f8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe610e1f6881908f10070ba64643cf |
completed | May 8, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69fe604c6c008190ad659e9b9fa82f7b |
completed | May 8, 2026, 10:14 p.m. |
| PDg | Predicate description generation | batch_69fe610d75a48190bfd08a9bb957fcd3 |
completed | May 8, 2026, 10:17 p.m. |
Created at: April 29, 2026, 9:17 p.m.