Triple
T15814218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pratt & Whitney Wasp |
E383432
|
entity |
| Predicate | applicationEra |
P36703
|
FINISHED |
| Object | late 1920s |
—
|
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 1920s | Statement: [Pratt & Whitney Wasp, applicationEra, late 1920s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: applicationEra Context triple: [Pratt & Whitney Wasp, applicationEra, late 1920s]
-
A.
appliesToEra
chosen
Indicates that something is relevant, valid, or in effect during a particular historical or temporal era.
-
B.
serviceEra
Indicates the historical period or era during which a service, role, or duty was performed.
-
C.
notablePlatformEra
Indicates that an entity is notably associated with a particular platform during a specific era or period of prominence.
-
D.
screenTimeEra
Indicates the period or era during which a particular screen-based technology, medium, or usage pattern is prevalent or characteristic.
-
E.
brandEra
Indicates the historical period or era during which a particular brand identity, style, or strategy is in 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_69d86da2858c819090cc8481e7207b6e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0c4a1571881909488728f123865ad |
completed | April 16, 2026, 11:14 a.m. |
| PD | Predicate disambiguation | batch_69e0053b847c8190945726c3ddac21cc |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:49 a.m.