Triple
T35973630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Que (Cilician kingdom) |
E1040352
|
entity |
| Predicate | hasEthnoLinguisticCharacter |
P115409
|
FINISHED |
| Object | Luwian |
—
|
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: Luwian | Statement: [Que (Cilician kingdom), hasEthnoLinguisticCharacter, Luwian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEthnoLinguisticCharacter Context triple: [Que (Cilician kingdom), hasEthnoLinguisticCharacter, Luwian]
-
A.
hasEthnolinguisticPresence
chosen
Indicates that a particular ethnolinguistic group is present or represented within a specified place, context, or population.
-
B.
hasEthnolinguisticContext
Indicates that something is associated with, shaped by, or understood within a specific ethnolinguistic (cultural and language-based) context.
-
C.
hasEthnicCharacteristic
Indicates that an entity possesses or is associated with a particular ethnic characteristic or identity.
-
D.
hasEthnicScope
Indicates that something is relevant or applicable specifically to a particular ethnic group or ethnic context.
-
E.
hasEthnonymRole
Indicates that an entity functions as an ethnonym, i.e., a name or label designating an ethnic group or people.
- 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_69f76e27758c81909b711cf38a130aaf |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
Created at: May 3, 2026, 4:07 p.m.