Triple
T29016020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CRIME attack |
E737308
|
entity |
| Predicate | disclosedAt |
P430
|
FINISHED |
| Object | Ekoparty Security Conference 2012 |
—
|
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: Ekoparty Security Conference 2012 | Statement: [CRIME attack, disclosedAt, Ekoparty Security Conference 2012]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: disclosedAt Context triple: [CRIME attack, disclosedAt, Ekoparty Security Conference 2012]
-
A.
yearOfPublicDisclosure
Indicates the calendar year in which information, an invention, or other subject matter was first publicly disclosed.
-
B.
announcedAt
chosen
Indicates that an announcement or declaration was made at a specific time or event.
-
C.
displayedAt
Indicates that one entity is presented or exhibited at a particular location, venue, or event.
-
D.
revealedAfter
Indicates that one piece of information, event, or state becomes known or disclosed only subsequent to another specified point in time or condition.
-
E.
discloses
Indicates that one entity reveals, makes known, or provides previously non-public information to another entity or to the public.
- 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_69f077ee19f881909af48f9cab00a2e5 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f65fe0772881909b1fbc2e28a1206a |
completed | May 2, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69f659d297cc8190b2b962ba30a1edb3 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 9:45 a.m.