Triple
T28388267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | joint parliamentary scrutiny group for Europol |
E719081
|
entity |
| Predicate | mayHoldMeetingsIn |
P60588
|
FINISHED |
| Object | Strasbourg |
—
|
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: Strasbourg | Statement: [joint parliamentary scrutiny group for Europol, mayHoldMeetingsIn, Strasbourg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayHoldMeetingsIn Context triple: [joint parliamentary scrutiny group for Europol, mayHoldMeetingsIn, Strasbourg]
-
A.
mayMeet
Indicates that one entity is permitted or has the possibility to meet or come together with another entity.
-
B.
mayMeetAt
chosen
Indicates that two or more entities are permitted or able to have a meeting or encounter at a specified place or time.
-
C.
mayAttend
Indicates that an entity is permitted or eligible to be present at or participate in a particular event, activity, or gathering.
-
D.
meetsTo
Indicates that one entity comes together with another at a specific time and place for an encounter, appointment, or interaction.
-
E.
meetsRegarding
Indicates that one entity meets with another specifically to discuss or address a particular topic, issue, or subject.
- 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_69eff6ef211081909d31d9be5f5567e6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64ceac7d48190be9d0929bcafd4bb |
completed | May 2, 2026, 7:13 p.m. |
| PD | Predicate disambiguation | batch_69f641e2f1708190b45b48d6a43c51d2 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 28, 2026, 1:11 a.m.