Triple
T23409247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hla’alua |
E560018
|
entity |
| Predicate | hasOwnLanguage |
P152149
|
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: [Hla’alua, hasOwnLanguage, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOwnLanguage Context triple: [Hla’alua, hasOwnLanguage, true]
-
A.
hasLanguages
Indicates that an entity is associated with one or more languages it uses, supports, or is expressed in.
-
B.
hasLanguageOn
Indicates that an entity uses or is associated with a particular language in a specific context, medium, or location.
-
C.
hasPrimaryLanguage1
Indicates that an entity’s main or most commonly used language is the specified language.
-
D.
hasRepresentativeLanguage
Indicates that an entity is associated with a language that serves as its primary or officially recognized means of representation or communication.
-
E.
hasLanguageInUniverse
Indicates that a particular language exists or is used within a specified fictional or conceptual universe.
- 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_69e2454b3a5881909c64773dc8a5d289 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a50fff10819094e71fb0c11b7d95 |
completed | April 29, 2026, 6:28 a.m. |
| PD | Predicate disambiguation | batch_69f061ed34288190a2e5e8cae03b0095 |
completed | April 28, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f07cbbd7488190ab3c8ae7d0fb68bf |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 17, 2026, 5:38 p.m.