Triple
T33076878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ECRYPT II |
E846387
|
entity |
| Predicate | includesInitiative |
P82385
|
FINISHED |
| Object | eSTREAM |
E235258
|
NE 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: eSTREAM | Statement: [ECRYPT II, includesInitiative, eSTREAM]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesInitiative Context triple: [ECRYPT II, includesInitiative, eSTREAM]
-
A.
exportInitiative
Indicates an action or relationship where an entity initiates or carries out the process of sending goods, services, or resources from one jurisdiction to another.
-
B.
initiative
Indicates that an entity takes the first step or leads in starting an action, project, or process without external prompting.
-
C.
coreInitiative
chosen
Indicates that an entity serves as a primary, central, or foundational initiative within a broader program, strategy, or effort.
-
D.
supportedInitiative
Indicates that an entity provided backing, endorsement, or assistance to a particular initiative or project.
-
E.
typeOfInitiative
Indicates that an initiative belongs to or is categorized under a particular type or classification.
- F. None of above.
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_69f3495405b88190967af2157b43b896 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a0249374a8c8190ab19002a123da439 |
completed | May 11, 2026, 9:25 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a35813621e8819090fe86224c3b0562 |
completed | June 19, 2026, 5:49 p.m. |
| PD | Predicate disambiguation | batch_6a02486194b08190a489ae3a8f4a59a9 |
completed | May 11, 2026, 9:21 p.m. |
Created at: May 1, 2026, 1:25 a.m.