Triple
T37027476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | N-1 Norge |
E916394
|
entity |
| Predicate | historicDomain |
P65445
|
FINISHED |
| Object | history of 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: history of aviation | Statement: [N-1 Norge, historicDomain, history of aviation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicDomain Context triple: [N-1 Norge, historicDomain, history of aviation]
-
A.
historicFor
chosen
Indicates that something holds historical significance or importance specifically in relation to another entity.
-
B.
historicCore
Indicates that something is part of, located within, or associated with the original historic center or oldest developed area of a place.
-
C.
historicState
Indicates that an entity was formerly a state or political entity in the past but no longer holds that status in the present.
-
D.
historicNetwork
Indicates a relationship where entities are or were connected through a historically significant network, system, or set of interactions.
-
E.
historicDenomination
Indicates that an entity was formerly associated with a particular religious denomination or branch in the past, even if that affiliation has since changed.
- 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_69f76e92c7648190bcfa277f64c71a21 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a017114e7148190b7479284c316443d |
completed | May 11, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_6a016eebd60481909212e2a49ef95fbe |
completed | May 11, 2026, 5:53 a.m. |
Created at: May 3, 2026, 4:14 p.m.