Triple
T11208816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swift F.1 |
E265247
|
entity |
| Predicate | usedInConflictPeriod |
P56075
|
FINISHED |
| Object | post–Second World War period |
—
|
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: post–Second World War period | Statement: [Swift F.1, usedInConflictPeriod, post–Second World War period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInConflictPeriod Context triple: [Swift F.1, usedInConflictPeriod, post–Second World War period]
-
A.
usedInConflictType
Indicates that something (such as a resource, method, or capability) is employed or applied within a specific type or category of conflict.
-
B.
conflictPeriod
Indicates the time span during which a particular conflict or dispute is occurring or in effect between the related entities.
-
C.
implementedDuringConflict
Indicates that an action, policy, or measure was carried out while an active conflict or war was ongoing.
-
D.
existedDuringConflict
chosen
Indicates that an entity was present or active for some or all of the duration of a specified conflict.
-
E.
usedBetween
Indicates that something serves as a means, medium, or shared resource connecting or operating jointly between two entities.
- 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_69d6aac59460819089b9848b27f57848 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8d5f8908190903817f84c629ba1 |
completed | April 9, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69d75cf83464819087529d47d025d313 |
completed | April 9, 2026, 8:02 a.m. |
Created at: April 8, 2026, 9:30 p.m.