Triple
T25341939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NATO Double-Track Decision |
E635435
|
entity |
| Predicate | locationOfDecision |
P52146
|
FINISHED |
| Object | Brussels |
—
|
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: Brussels | Statement: [NATO Double-Track Decision, locationOfDecision, Brussels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfDecision Context triple: [NATO Double-Track Decision, locationOfDecision, Brussels]
-
A.
decisionPlace
chosen
Indicates the location where a decision is made or formally determined.
-
B.
decisionMakingArea
Indicates the area or domain within which a decision is made or for which a decision-making process is responsible.
-
C.
decisionPointFor
Indicates a point in a process or workflow at which a choice must be made that determines which subsequent path or outcome will follow.
-
D.
judgmentLocationFor
Indicates the place or venue where a judgment, decision, or evaluative determination about an entity is made or recorded.
-
E.
subjectLocation
Indicates that one entity is located at, in, or near the place or position specified by another entity.
- 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_69e75a99bd6481909476115b35b9a8e4 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f6f8565134819096aac0175f924a9f |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
Created at: April 21, 2026, 1:32 p.m.