Triple
T6470329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Almaza Airport |
E142331
|
entity |
| Predicate | hasApproximateOpeningPeriod |
P30383
|
FINISHED |
| Object | early 20th century |
—
|
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 20th century | Statement: [Almaza Airport, hasApproximateOpeningPeriod, early 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateOpeningPeriod Context triple: [Almaza Airport, hasApproximateOpeningPeriod, early 20th century]
-
A.
openingTime
Indicates the time at which a place, service, or event begins operating or becomes accessible.
-
B.
openedAt
chosen
Indicates that an entity began operating, became accessible, or was first made available at a specific time or date.
-
C.
openingBeganApproxMa
Indicates the approximate time in millions of years ago when an opening or separation process (such as rifting or basin formation) began.
-
D.
hasOpeningType
Indicates that one entity has, features, or is characterized by a particular type or kind of opening.
-
E.
isOpenTo
Indicates that one entity is receptive, willing, or available to consider, accept, or engage with another entity or proposal.
- 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_69c008d3bf4c8190bcf798c5ba9d6fb3 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06a2e896481908ed004e3b0a33121 |
completed | March 22, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69c0673d46a08190bc8bcd29f9555fe7 |
completed | March 22, 2026, 10:03 p.m. |
Created at: March 22, 2026, 4:50 p.m.