Triple
T9269218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pero |
E222779
|
entity |
| Predicate | hasGlottologEntry |
P87885
|
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: [Pero, hasGlottologEntry, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGlottologEntry Context triple: [Pero, hasGlottologEntry, yes]
-
A.
hasGlottologName
Indicates that an entity is associated with a specific name as recorded in the Glottolog linguistic database.
-
B.
hasGlottologReference
Indicates that an entity is associated with a specific reference entry in the Glottolog linguistic database.
-
C.
hasEthnologueEntry
Indicates that there exists an entry for the subject in the Ethnologue language reference resource.
-
D.
glottocode
Indicates the standardized Glottolog code that uniquely identifies the language or dialect associated with an entity.
-
E.
glottologStatus
Indicates the classification or status of a language or dialect as defined in the Glottolog database.
- 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_69ca841ffe208190aa7bcffbef2f8379 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd074ef7408190b213c09491918132 |
completed | April 1, 2026, 11:53 a.m. |
| PD | Predicate disambiguation | batch_69cc7a537bbc8190baee71f556e52a7b |
completed | April 1, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69cc95597be081908ece2491dd2f0f74 |
completed | April 1, 2026, 3:47 a.m. |
Created at: March 30, 2026, 7:33 p.m.