Triple
T1692910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Europol |
E36588
|
entity |
| Predicate | directorSince |
P31396
|
FINISHED |
| Object | 2018-05-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: 2018-05-01 | Statement: [Europol, directorSince, 2018-05-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directorSince Context triple: [Europol, directorSince, 2018-05-01]
-
A.
director
Indicates that one entity serves as the director (creative or managerial leader) of another entity, such as a film, organization, or project.
-
B.
filmDirectorOfAppearance
Indicates that a person served as the director for a specific appearance or segment within a film or audiovisual work.
-
C.
strategyDirectedBy
Indicates that the development, implementation, or oversight of a strategy is guided or controlled by a specified directing entity.
-
D.
featureDirectorialDebutOf
Indicates that a work (typically a film) serves as the first directorial effort of a particular director.
-
E.
notableDirector
Indicates that a person has directed a work (such as a film or show) in a way that is recognized as significant or distinguished.
- 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_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. |
| PDg | Predicate description generation | batch_69aaf33347e48190a32b6d0099e3d389 |
completed | March 6, 2026, 3:30 p.m. |
Created at: March 4, 2026, 7:29 p.m.