Triple
T18005714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boeing 377 Stratocruiser |
E430740
|
entity |
| Predicate | primaryEraOfOperation |
P77920
|
FINISHED |
| Object | late 1940s |
—
|
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 1940s | Statement: [Boeing 377 Stratocruiser, primaryEraOfOperation, late 1940s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryEraOfOperation Context triple: [Boeing 377 Stratocruiser, primaryEraOfOperation, late 1940s]
-
A.
primaryEraEvaluated
Indicates that an entity has been assessed or analyzed with respect to its main or most relevant historical era or time period.
-
B.
originalRunEra
Indicates the time period or era during which something (such as a show, series, or product) was first originally run or released.
-
C.
hasPrimaryEra
chosen
Indicates that an entity is chiefly associated with or belongs to a particular historical or temporal era.
-
D.
initiallyOperated
Indicates that an entity first began functioning, being used, or carrying out its intended operation at a specified initial time or under initial conditions.
-
E.
operatedSince
Indicates that an entity has been in operation continuously from a specified starting time or date.
- 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_69d8b904530081908bf341d842464856 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4b51ba1888190a339d726e92f376b |
completed | April 19, 2026, 10:57 a.m. |
| PD | Predicate disambiguation | batch_69e3f90039e4819080527f860dca042e |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:24 a.m.