Triple
T9944047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PB4Y-2 Privateer |
E194155
|
entity |
| Predicate | usedExtensivelyDuring |
P11801
|
FINISHED |
| Object | late World War II Pacific operations |
—
|
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: late World War II Pacific operations | Statement: [PB4Y-2 Privateer, usedExtensivelyDuring, late World War II Pacific operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedExtensivelyDuring Context triple: [PB4Y-2 Privateer, usedExtensivelyDuring, late World War II Pacific operations]
-
A.
usedDuring
Indicates that one entity is employed, applied, or active in the course of another entity’s process, event, or time period.
-
B.
widelyUsedIn
chosen
Indicates that something is commonly or extensively utilized within a particular context, domain, or group.
-
C.
usedOver
Indicates that one entity has been utilized, applied, or consumed in relation to another entity, typically as a resource, medium, or tool in a particular context or period.
-
D.
usedAcross
Indicates that something is utilized or applied in multiple different contexts, locations, or domains.
-
E.
oftenUsedAfter
Indicates that one entity is frequently or typically used immediately following another entity in a sequence or workflow.
- 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_69ca82e409348190a393777356b80a2a |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb613fbb48190b82a06987310cc96 |
completed | April 2, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9428cc81909b4b4938566d78a7 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:45 p.m.