Triple
T23915862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Engan languages |
E602079
|
entity |
| Predicate | haveNotableLanguage |
P207
|
FINISHED |
| Object | Enga 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: Enga language | Statement: [Engan languages, haveNotableLanguage, Enga language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haveNotableLanguage Context triple: [Engan languages, haveNotableLanguage, Enga language]
-
A.
hasOwnLanguage
Indicates that an entity possesses or uses a distinct language of its own.
-
B.
hasSignificantLanguage
chosen
Indicates that an entity possesses a language that plays an important or primary role in its communication, identity, or functioning.
-
C.
hasContactWithLanguage
Indicates that an entity has some form of interaction, exposure, or engagement with a particular language.
-
D.
hasLanguageOn
Indicates that an entity uses or is associated with a particular language in a specific context, medium, or location.
-
E.
hasNotableLanguageWithOfficialStatusIn
Indicates that a language holds an officially recognized and notable status within a specified jurisdiction or region.
- 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_69e2953a187081908346a9f36e85fc98 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1ce9917808190ad66a4e276a24b3d |
completed | April 29, 2026, 9:25 a.m. |
| PD | Predicate disambiguation | batch_69f16151ebdc819086e9e1d7cc1f4f3c |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:40 p.m.