Triple
T37471581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kyrian (language) |
E931165
|
entity |
| Predicate | primaryUseInGame |
P75305
|
FINISHED |
| Object | ambient speech |
—
|
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: ambient speech | Statement: [Kyrian (language), primaryUseInGame, ambient speech]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryUseInGame Context triple: [Kyrian (language), primaryUseInGame, ambient speech]
-
A.
primaryUseByPlayers
Indicates the main way in which players typically use or interact with the referenced entity.
-
B.
primaryUseDuringGames
chosen
Indicates that something is mainly used or employed during games or gameplay activities.
-
C.
primaryUseOf
Indicates that one entity serves as the main or principal function, purpose, or application of another entity.
-
D.
skillUsedFor
Indicates that a particular skill is employed or applied to perform, achieve, or facilitate a specific task, goal, or function.
-
E.
primaryFunctionInLore
Indicates that something’s main role or purpose is defined within a fictional or narrative lore context.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.