Triple
T14982819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trident 2E |
E373621
|
entity |
| Predicate | jetAge |
P99184
|
FINISHED |
| Object | second-generation jet airliner |
—
|
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: second-generation jet airliner | Statement: [Trident 2E, jetAge, second-generation jet airliner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: jetAge Context triple: [Trident 2E, jetAge, second-generation jet airliner]
-
A.
riftAge
Indicates the age or time since formation of a geological rift or rift-related feature.
-
B.
ageInPlay
Indicates that an entity’s age is relevant or applicable within the context of a particular play, game, or interactive scenario.
-
C.
hasJetAgeSignificance
chosen
Indicates that something holds particular importance, influence, or relevance within the context of the Jet Age era of aviation.
-
D.
ageAtIntroduction
Indicates the age an entity had at the time it was first introduced or presented in a given context.
-
E.
typicalAge
Indicates the usual or characteristic age associated with an entity, event, or condition.
- 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_69d85ccbbcd48190acb56e7cf104d8ad |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded6fe42a081909308f788fdf024d5 |
completed | April 15, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69de9a6169b48190a679609febd2d0e3 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:52 a.m.