Triple
T29010830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IPP |
E736560
|
entity |
| Predicate | defaultScheme |
P114887
|
FINISHED |
| Object | ipp:// |
—
|
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: ipp:// | Statement: [IPP, defaultScheme, ipp://]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defaultScheme Context triple: [IPP, defaultScheme, ipp://]
-
A.
defaultDriver
Indicates that one entity is designated as the primary or standard driver for another entity (such as a vehicle or account).
-
B.
defaultOn
Indicates that something is in an enabled or active state by default, without requiring explicit activation.
-
C.
defaultRemote
Indicates that one entity is designated as the primary or standard remote counterpart used by another entity for communication, synchronization, or access.
-
D.
defaultValue
Indicates that one entity serves as the pre-assigned or fallback value automatically used for another entity when no explicit value is provided.
-
E.
usesScheme
chosen
Indicates that one entity employs, follows, or is based on a particular scheme, method, or structured plan associated with 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_69f077eb81e88190ad9ff62cbb9f555e |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f73ae120bc8190bff94d38d7a7a00d |
completed | May 3, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69f73a38d0848190aa5139144b8561c6 |
completed | May 3, 2026, 12:06 p.m. |
Created at: April 28, 2026, 9:42 a.m.