Triple
T29389516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | android.print.PrinterId |
E745337
|
entity |
| Predicate | identifierComponents |
P70833
|
FINISHED |
| Object | print service component name |
—
|
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: print service component name | Statement: [android.print.PrinterId, identifierComponents, print service component name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: identifierComponents Context triple: [android.print.PrinterId, identifierComponents, print service component name]
-
A.
identifierFor
Indicates that one entity serves as a unique identifying label or code for another entity.
-
B.
identifiedIn
Indicates that an entity is recognized, discovered, or documented within a specified source, context, or location.
-
C.
designationComponent
chosen
Indicates that one entity functions as a component or constituent part of another entity’s designation or formal naming.
-
D.
identifiedUsing
Indicates that one entity was recognized, distinguished, or determined by means of a specified method, tool, or identifier.
-
E.
isComponentOfNameOf
Indicates that one entity is the name of a component or part belonging to 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_69f67d3624248190a36a9b2d2e9778d4 |
completed | May 2, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 28, 2026, 2:41 p.m.