Triple
T712549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Android Dalvik VM |
E14240
|
entity |
| Predicate | replacedInVersion |
P3618
|
FINISHED |
| Object | Android 5.0 Lollipop by ART |
—
|
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: Android 5.0 Lollipop by ART | Statement: [Android Dalvik VM, replacedInVersion, Android 5.0 Lollipop by ART]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedInVersion Context triple: [Android Dalvik VM, replacedInVersion, Android 5.0 Lollipop by ART]
-
A.
replacedSystemUsedUntil
chosen
Indicates that one system was used up until it was replaced by another system.
-
B.
placedBy
Indicates that one entity was positioned, set, or put in a location or context by another entity.
-
C.
replacedInterface
Indicates that one interface has been substituted or superseded by another interface.
-
D.
usedInVersionRange
Indicates that something is applicable, valid, or in effect only within a specified range of versions.
-
E.
previousVersionAdopted
Indicates that one entity has been adopted or implemented as a successor to an earlier version represented by the other entity.
- 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_69a4934a36e081909e7abef98b898a4e |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a77fcc6881908a025bb21e44ad56 |
completed | March 1, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69a4a4f221b081909fbaa689fb20eb3e |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:36 p.m.