Triple
T29389203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PrintManager |
E745330
|
entity |
| Predicate | hidesImplementationDetail |
P166710
|
FINISHED |
| Object | printer discovery logic |
—
|
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: printer discovery logic | Statement: [PrintManager, hidesImplementationDetail, printer discovery logic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hidesImplementationDetail Context triple: [PrintManager, hidesImplementationDetail, printer discovery logic]
-
A.
hasImplementationDetail
Indicates that one entity specifies or contains a concrete implementation detail or internal mechanism related to another entity.
-
B.
hidesFrom
Indicates that one entity actively avoids being seen, detected, or encountered by another entity.
-
C.
helpedHide
Indicates that one entity assisted another in concealing or keeping something or someone hidden.
-
D.
hiddenIn
Indicates that one entity is concealed within, behind, or inside another entity so that it is not readily visible or apparent.
-
E.
hiddenAt
Indicates that one entity is concealed or stored at a specific location or within another entity.
- F. None of above. chosen
Provenance (4 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_69f669d578608190962d35116a01420c |
completed | May 2, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69f660f4f7a88190b93c60d76b86c912 |
completed | May 2, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69f661b47d088190934f63884a203261 |
completed | May 2, 2026, 8:42 p.m. |
Created at: April 28, 2026, 2:41 p.m.