Triple
T10586531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alpha Capricorni |
E249867
|
entity |
| Predicate | traditionalNameOriginLanguage |
P28203
|
FINISHED |
| Object | Arabic |
—
|
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: Arabic | Statement: [Alpha Capricorni, traditionalNameOriginLanguage, Arabic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalNameOriginLanguage Context triple: [Alpha Capricorni, traditionalNameOriginLanguage, Arabic]
-
A.
traditionalLanguageName
Indicates the name traditionally used in a particular language to refer to the subject entity.
-
B.
originalNameLanguage
chosen
Indicates that the specified language is the language in which an entity’s original or primary name was expressed.
-
C.
hasTraditionalName
Indicates that an entity is associated with a name traditionally used or recognized for it, often rooted in long-standing cultural or historical practice.
-
D.
countryOfNamingTradition
Indicates the country whose cultural or linguistic naming conventions are used to form or interpret a given name.
-
E.
languageOfHistoricName
Indicates the language in which a historic or former name of an entity is expressed.
- 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_69d381c9d3d48190a29ee491e1696a0e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d527698be48190a2f5e573d7cc0661 |
completed | April 7, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69d51907b2b881908ab9a8594688ee06 |
completed | April 7, 2026, 2:47 p.m. |
Created at: April 6, 2026, 12:39 p.m.