Triple
T35179953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Binnenlandse Strijdkrachten |
E1015819
|
entity |
| Predicate | formedNearEndOf |
P120372
|
FINISHED |
| Object | Second World War |
—
|
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: Second World War | Statement: [Binnenlandse Strijdkrachten, formedNearEndOf, Second World War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formedNearEndOf Context triple: [Binnenlandse Strijdkrachten, formedNearEndOf, Second World War]
-
A.
assembledNearEndOf
Indicates that one entity is put together or constructed in close proximity to the endpoint or final section of another entity.
-
B.
nearFinishOf
chosen
Indicates that one entity is located close to the endpoint or finishing section of another entity.
-
C.
formsNear
Indicates that one entity takes shape or comes into existence in close spatial proximity to another entity.
-
D.
formedWithin
Indicates that one entity was created, established, or came into existence inside the spatial or structural bounds of another entity.
-
E.
formedTo
Indicates that one entity was created, established, or organized for the purpose of serving, supporting, or enabling another entity or activity.
- 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_69f76ddcc108819097f96853b7ed9ef4 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a0048697bd081909073640666ca6a96 |
completed | May 10, 2026, 8:57 a.m. |
| PD | Predicate disambiguation | batch_6a0047bf3c248190a9ac97a7afdfe2cb |
completed | May 10, 2026, 8:54 a.m. |
Created at: May 3, 2026, 4:02 p.m.