Triple
T29014902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blueprint protocol |
E737276
|
entity |
| Predicate | publiclySharedAs |
P192705
|
FINISHED |
| Object | open protocol |
—
|
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: open protocol | Statement: [Blueprint protocol, publiclySharedAs, open protocol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publiclySharedAs Context triple: [Blueprint protocol, publiclySharedAs, open protocol]
-
A.
canBeSharedTo
Indicates that something is capable of being shared or distributed to a particular recipient or destination.
-
B.
sharesUniverseWith
Indicates that two entities exist within the same fictional or narrative universe, implying shared continuity, setting, or canon.
-
C.
exportShare
Indicates the proportion of an entity’s total output or activity that is sold or transferred to external markets or destinations.
-
D.
sharesWith
Indicates that one entity gives another entity access to or use of something it possesses.
-
E.
isSharedBy
Indicates that something is jointly possessed, used, or experienced by two or more entities.
- 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_69f077ee19f881909af48f9cab00a2e5 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fd2839880c819099a7a89783f2270e |
completed | May 8, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69fd23dc5da48190ae8ba08947d34956 |
completed | May 7, 2026, 11:44 p.m. |
| PDg | Predicate description generation | batch_69fd28379d2c8190903ba228ee1cc756 |
completed | May 8, 2026, 12:03 a.m. |
Created at: April 28, 2026, 9:45 a.m.