Triple
T678185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nijmegen |
E13123
|
entity |
| Predicate | wasObjectiveIn |
P6636
|
FINISHED |
| Object | Allied advance in 1944 |
—
|
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: Allied advance in 1944 | Statement: [Nijmegen, wasObjectiveIn, Allied advance in 1944]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasObjectiveIn Context triple: [Nijmegen, wasObjectiveIn, Allied advance in 1944]
-
A.
protectionObjective
Indicates that one entity has the goal or purpose of safeguarding, defending, or preserving another entity or its interests.
-
B.
hasPrimaryGoal
Indicates that an entity’s main or most important objective is the specified goal.
-
C.
goals
chosen
Indicates that an entity has objectives, targets, or desired outcomes it aims to achieve.
-
D.
wonFor
Indicates that one entity received an award, prize, or recognition specifically on behalf of or representing another entity.
-
E.
aimedToImplement
Indicates that an entity had the intention or plan to carry out, realize, or put another entity (such as a policy, idea, or system) into effect.
- 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_69a4933d3bf88190972041cd8cf143b9 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4a04e17088190943d54977eb3f83a |
completed | March 1, 2026, 8:23 p.m. |
| PD | Predicate disambiguation | batch_69a49d1bbd0c81909cfbec30bd17bde7 |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.