Triple
T29389415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | android.print.PrintAttributes |
E745335
|
entity |
| Predicate | supportsBuilderPattern |
P29142
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [android.print.PrintAttributes, supportsBuilderPattern, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsBuilderPattern Context triple: [android.print.PrintAttributes, supportsBuilderPattern, true]
-
A.
supportsCodeBuilder
Indicates that an entity provides compatibility with or functionality for a code-building tool or environment.
-
B.
supportsPatternType
chosen
Indicates that one entity is compatible with, or capable of handling, a specified pattern type.
-
C.
hasBuildingPattern
Indicates that an entity exhibits or follows a particular architectural or structural building pattern.
-
D.
builder
Indicates that an entity is responsible for constructing, creating, or assembling another entity.
-
E.
hasBuilderType
Indicates that an entity is associated with or characterized by a specific type or category of builder.
- 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_69f0a79dfabc81908755382ee47791e2 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_6a033029023481909d9fa4a76b954879 |
completed | May 12, 2026, 1:50 p.m. |
| PD | Predicate disambiguation | batch_6a032d9f1fa48190bd1c94a8f930d02c |
completed | May 12, 2026, 1:39 p.m. |
Created at: April 28, 2026, 2:41 p.m.