Triple
T25535810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Android platform tools |
E640034
|
entity |
| Predicate | downloadableFrom |
P90390
|
FINISHED |
| Object | Android developer website |
—
|
NE NERFINISHED |
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 developer website | Statement: [Android platform tools, downloadableFrom, Android developer website]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: downloadableFrom Context triple: [Android platform tools, downloadableFrom, Android developer website]
-
A.
downloadFrom
chosen
Indicates that a file, data, or resource is transferred and obtained from a specified source or provider.
-
B.
supportsDigitalDownloads
Indicates that one entity enables or allows the other entity to provide or access digital file downloads.
-
C.
distributesFrom
Indicates that something acts as the source or origin from which items, resources, or information are distributed to others.
-
D.
distributionIncludes
Indicates that a distribution or release of something contains or encompasses the specified item or component.
-
E.
distributionPackage
Indicates that one entity is a package or bundle used to distribute another entity (such as software, content, or resources).
- 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_69e75dbfff7081909b0aa779d48321d2 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f89056b481908f02d5d6d2837bfd |
completed | May 2, 2026, 1:13 p.m. |
| PD | Predicate disambiguation | batch_69f468421ba08190880eac99135e5970 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 3:22 p.m.