Triple
T1692896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Europol |
E36588
|
entity |
| Predicate | cameIntoOperation |
P21563
|
FINISHED |
| Object | 1999-07-01 |
—
|
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: 1999-07-01 | Statement: [Europol, cameIntoOperation, 1999-07-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cameIntoOperation Context triple: [Europol, cameIntoOperation, 1999-07-01]
-
A.
firstOperationalUse
Indicates the point in time or context when something is used operationally for the very first time.
-
B.
becameOperational
chosen
Indicates that an entity transitioned from a non-functioning or inactive state to an active, functioning, or service-ready state at a certain point in time.
-
C.
commissionedInService
Indicates that an entity was formally brought into active service or duty within a particular organization, role, or context.
-
D.
cameIntoForceInYear
Indicates that a law, agreement, or formal measure became legally effective or operational in a specified calendar year.
-
E.
beganCivilOperations
Indicates that an entity initiated or commenced civil (non-military) administrative or operational activities in relation to another entity or context.
- 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_69a886151508819084fa7f1ce6e05577 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aaf3359ce48190803b322db8ad6027 |
completed | March 6, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69aa61b71cec8190b273588051058ebd |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:29 p.m.