Triple
T29504851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IPP Everywhere |
E748482
|
entity |
| Predicate | usesDiscoveryProtocol |
P98632
|
FINISHED |
| Object | DNS-SD |
—
|
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: DNS-SD | Statement: [IPP Everywhere, usesDiscoveryProtocol, DNS-SD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesDiscoveryProtocol Context triple: [IPP Everywhere, usesDiscoveryProtocol, DNS-SD]
-
A.
usesNeighborDiscovery
Indicates that an entity employs a neighbor discovery mechanism to detect, identify, or maintain information about adjacent or nearby entities in a network or environment.
-
B.
hasDiscoveryFeature
chosen
Indicates that an entity includes or supports a capability for discovering, finding, or surfacing other relevant entities, items, or information.
-
C.
supportedDiscoveryOf
Indicates that one entity aided, enabled, or contributed to another entity’s act of discovering something.
-
D.
hasDiscoveryStatus
Indicates the current state or phase of discovery or identification associated with an entity.
-
E.
hasNearbyDiscovery
Indicates that one entity has a discovery located in close physical or spatial proximity to it.
- 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_69f0bd455a9c8190b40a3e8ea38cf61f |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f69dfdda708190be290c7bec205445 |
completed | May 3, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 28, 2026, 4:27 p.m.