Triple
T37227926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Max |
E923054
|
entity |
| Predicate | settingEraInspiration |
P132209
|
FINISHED |
| Object | World War I aviation |
—
|
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: World War I aviation | Statement: [Red Max, settingEraInspiration, World War I aviation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingEraInspiration Context triple: [Red Max, settingEraInspiration, World War I aviation]
-
A.
curatesEra
Indicates a relationship where an entity organizes, selects, or manages items, information, or works specifically associated with a particular historical or thematic era.
-
B.
hasEraInfluence
chosen
Indicates that one era or time period has a significant impact on shaping the characteristics, developments, or outcomes of another.
-
C.
eraOfSetting
Indicates the historical or temporal period in which the setting of something (such as a story, event, or work) takes place.
-
D.
creatorEra
Indicates the historical period or era during which the creator of an entity was active or produced the entity.
-
E.
introductionEra
Indicates the historical period or era during which something was first introduced or came into use.
- 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_69f76ea7f0008190b31b8e30f3d05a71 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd7e364a648190a1e9e1d9fc76e99e |
completed | May 8, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69fd7bb547608190a3b04dddbca6b8bc |
completed | May 8, 2026, 5:59 a.m. |
Created at: May 3, 2026, 4:15 p.m.