Triple
T2447620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Picture Transfer Protocol |
E53630
|
entity |
| Predicate | supportsTransferOf |
P38153
|
FINISHED |
| Object | digital photographs |
—
|
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: digital photographs | Statement: [Picture Transfer Protocol, supportsTransferOf, digital photographs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsTransferOf Context triple: [Picture Transfer Protocol, supportsTransferOf, digital photographs]
-
A.
allowsTransferTo
chosen
Indicates that one entity permits or enables the transfer of something (such as rights, funds, or data) to another specified entity.
-
B.
hasTransfer
Indicates a relationship where something is moved or conveyed from one entity or location to another.
-
C.
supportsUse
Indicates that one entity enables, allows, or is compatible with the use or operation of another entity.
-
D.
supportsReferral
Indicates that one entity enables, accepts, or facilitates referrals being made to another entity or service.
-
E.
supportsValidationOf
Indicates that one entity provides the mechanisms or conditions necessary for another entity to be checked or verified for correctness or compliance.
- 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_69ab495d227c8190b26ae6548eeb1019 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd2bc7b5481908b3664495e99f1a4 |
completed | March 7, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69abd0aed2688190a18fe66b98d80e0b |
completed | March 7, 2026, 7:15 a.m. |
Created at: March 6, 2026, 9:43 p.m.