Triple
T284202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NATO Headquarters, Brussels, Belgium |
E5852
|
entity |
| Predicate | meetingVenueFor |
P373
|
FINISHED |
| Object | NATO summits (when hosted in Brussels) |
—
|
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: NATO summits (when hosted in Brussels) | Statement: [NATO Headquarters, Brussels, Belgium, meetingVenueFor, NATO summits (when hosted in Brussels)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meetingVenueFor Context triple: [NATO Headquarters, Brussels, Belgium, meetingVenueFor, NATO summits (when hosted in Brussels)]
-
A.
meetingType
Indicates the specific category or format of a meeting that characterizes how it is organized or conducted.
-
B.
meetingCity
Indicates the city where a meeting or encounter between entities takes place.
-
C.
venue
chosen
Indicates the place or location where an event, activity, or interaction takes place.
-
D.
meetsBy
Indicates that one entity encounters or comes together with another entity, typically at a specific time or place.
-
E.
convenesIn
Indicates that an entity brings together or assembles a group, meeting, or event at a specific place or venue.
- 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_69a25946a7ac8190a78871c210213272 |
completed | Feb. 28, 2026, 2:56 a.m. |
| NER | Named-entity recognition | batch_69a25e0d789881908d6a9a8d6a0d4a6c |
completed | Feb. 28, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69a25b795a6c8190944d48e8418e0ccd |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 3:02 a.m.