Triple
T29389411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | android.print.PrintAttributes |
E745335
|
entity |
| Predicate | hasNestedClass |
P166716
|
FINISHED |
| Object | android.print.PrintAttributes.Builder |
—
|
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.print.PrintAttributes.Builder | Statement: [android.print.PrintAttributes, hasNestedClass, android.print.PrintAttributes.Builder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNestedClass Context triple: [android.print.PrintAttributes, hasNestedClass, android.print.PrintAttributes.Builder]
-
A.
hasCoreClass
Indicates that an entity is associated with, or belongs to, a primary or fundamental class within a classification system.
-
B.
hasMultipleSubclasses
Indicates that a class or category is related to more than one distinct subclass within a hierarchy.
-
C.
isInnerClassOf
chosen
Indicates that one class is defined as a nested (inner) class within another class.
-
D.
includesClasses
Indicates that one entity contains or encompasses one or more class-type entities as part of its definition or structure.
-
E.
hasHigherClass
Indicates that one entity belongs to a higher rank, level, or category in a hierarchy than another 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_69f0a79dfabc81908755382ee47791e2 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69fe1fd637c08190aa95cd2478c278cb |
completed | May 8, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69fe19344bb481909b5e2144155e4add |
completed | May 8, 2026, 5:11 p.m. |
Created at: April 28, 2026, 2:41 p.m.