Triple
T35778679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Android Beta Program |
E1034371
|
entity |
| Predicate | softwareTypeTested |
P83486
|
FINISHED |
| Object | Android beta versions |
—
|
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 beta versions | Statement: [Android Beta Program, softwareTypeTested, Android beta versions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: softwareTypeTested Context triple: [Android Beta Program, softwareTypeTested, Android beta versions]
-
A.
softwareName
Indicates that one entity is the name or title of a software application associated with another entity.
-
B.
hasSoftwareType
chosen
Indicates that an entity is associated with or classified under a particular type or category of software.
-
C.
softwareFormat
Indicates that one entity specifies or uses the file or data format in which a software-related item is encoded, stored, or delivered.
-
D.
softwareTypeMaintained
Indicates that an entity is responsible for maintaining or supporting a particular type of software.
-
E.
softwareSystem
Indicates a relationship where an entity functions as, or is classified as, a software system.
- 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_69f76e14a1e081908eddd57bd6fdb3be |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a1fdf0408190a0e08958c4d5ad52 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a070e23881909a233370acb57384 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:06 p.m.