Triple
T4208405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aéropostale |
E93836
|
entity |
| Predicate | operationalEra |
P28914
|
FINISHED |
| Object | early commercial aviation era |
—
|
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: early commercial aviation era | Statement: [Aéropostale, operationalEra, early commercial aviation era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operationalEra Context triple: [Aéropostale, operationalEra, early commercial aviation era]
-
A.
originalRunEra
Indicates the time period or era during which something (such as a show, series, or product) was first originally run or released.
-
B.
partOfEra
Indicates that one entity exists as a temporal segment or component within the duration or scope of a larger historical era.
-
C.
eraOfOperation
chosen
Indicates the time period or span of years during which an entity was active or in operation.
-
D.
appliesToEra
Indicates that something is relevant, valid, or in effect during a particular historical or temporal era.
-
E.
recordingEra
Indicates the historical time period or era during which the recording was made.
- 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_69b3451743608190808f41d17ccf2650 |
completed | March 12, 2026, 10:58 p.m. |
| NER | Named-entity recognition | batch_69b34e098da881909a0cc339cc186627 |
completed | March 12, 2026, 11:36 p.m. |
| PD | Predicate disambiguation | batch_69b347efd9b08190bb50f82e4e7fe06d |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:03 p.m.