Triple
T29389637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | android.print.PrintAttributes.Resolution |
E745340
|
entity |
| Predicate | returnType:getId() |
P85669
|
FINISHED |
| Object | java.lang.String |
—
|
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: java.lang.String | Statement: [android.print.PrintAttributes.Resolution, returnType:getId(), java.lang.String]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnType:getId() Context triple: [android.print.PrintAttributes.Resolution, returnType:getId(), java.lang.String]
-
A.
parameterType:id
Indicates that the subject is identified as a specific parameter type by the given identifier.
-
B.
returnsToIdentityOf
Indicates that an entity reverts or is restored to its original or defining identity after a change, transformation, or deviation.
-
C.
typeOfIdentity
Indicates the specific category or nature of identity that characterizes or defines an entity within a given context.
-
D.
bodyReturnType
chosen
Indicates the data type of the value that a method or function returns in its response body.
-
E.
identifiableBy
Indicates that one entity can be uniquely recognized, distinguished, or referenced by another entity (such as an identifier, attribute, or feature).
- 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_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
Created at: April 28, 2026, 2:41 p.m.