Triple
T29014906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blueprint protocol |
E737276
|
entity |
| Predicate | promotedVia |
P174706
|
FINISHED |
| Object | YouTube |
—
|
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: YouTube | Statement: [Blueprint protocol, promotedVia, YouTube]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: promotedVia Context triple: [Blueprint protocol, promotedVia, YouTube]
-
A.
promotedWith
Indicates that one entity is advertised, marketed, or publicized together with another entity as part of the same promotional effort.
-
B.
promotedFrom
Indicates that an entity has advanced to a new position, role, or status from a specified prior one.
-
C.
promotedIn
Indicates that an entity was advanced to a higher rank, position, or status during a specified time or event.
-
D.
promotesFrom
Indicates that one entity advances or elevates another entity from a lower position, role, or status to a higher one.
-
E.
hasBeenPromotedBy
Indicates that one entity has received a promotion as a result of the decision or action taken by 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_69f077ee19f881909af48f9cab00a2e5 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6c5b7e46081909975b05f7298cc0e |
completed | May 3, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f6c49069e48190a3486b6254a6645b |
completed | May 3, 2026, 3:44 a.m. |
Created at: April 28, 2026, 9:45 a.m.