Triple
T575170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kotlin |
E13746
|
entity |
| Predicate | primaryUseOnAndroid |
P10000
|
FINISHED |
| Object | first-class language for Android development |
—
|
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: first-class language for Android development | Statement: [Kotlin, primaryUseOnAndroid, first-class language for Android development]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryUseOnAndroid Context triple: [Kotlin, primaryUseOnAndroid, first-class language for Android development]
-
A.
usedOn
Indicates that one entity is applied to, operated on, or otherwise utilized in relation to another entity.
-
B.
usageType
Indicates the specific manner, purpose, or context in which something is used or intended to be used.
-
C.
usesDevice
Indicates that one entity operates, employs, or relies on a particular device to perform an action or achieve a purpose.
-
D.
usedOnMode
Indicates that something is applied, operated, or functions specifically in a given mode or operational setting.
-
E.
usedPrimarilyIn
chosen
Indicates that something is mainly or most commonly employed within a particular context, domain, or purpose.
- 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_69a4933fa4d88190a7949cc83c08c5c1 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49b4c23548190a3b883239c7c78c8 |
completed | March 1, 2026, 8:02 p.m. |
| PD | Predicate disambiguation | batch_69a494c4969c819080375d08f9eec50c |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.