Triple
T33829763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HD 206859 |
E867063
|
entity |
| Predicate | hasProperNameOrigin |
P3325
|
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: [HD 206859, hasProperNameOrigin, Arabic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProperNameOrigin Context triple: [HD 206859, hasProperNameOrigin, Arabic]
-
A.
hasProperName
Indicates that an entity is associated with a specific proper name used to uniquely identify it.
-
B.
hasNameOriginType
Indicates that there is a specific type or category describing the origin of an entity’s name.
-
C.
hasNameOrigin
chosen
Indicates that the origin or source of an entity’s name is specified by the related entity.
-
D.
hasProperNameElement
Indicates that an entity’s proper name includes a specific component (such as a word, phrase, or segment) as one of its constituent elements.
-
E.
hasLocalNameOrigin
Indicates that the local or commonly used name of an entity originates from, or is derived from, a specified source (such as a language, place, or culture).
- 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_69f34991dd248190a659541588506b3c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a01d7b3ce8c8190b2f90be730505765 |
completed | May 11, 2026, 1:20 p.m. |
| PD | Predicate disambiguation | batch_6a01d5115a6c8190a6d9f96ec484135a |
completed | May 11, 2026, 1:09 p.m. |
Created at: May 1, 2026, 1:46 a.m.