Triple
T29547346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stepanakert Airport |
E749664
|
entity |
| Predicate | operationLimitationReason |
P20676
|
FINISHED |
| Object | political issues |
—
|
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: political issues | Statement: [Stepanakert Airport, operationLimitationReason, political issues]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operationLimitationReason Context triple: [Stepanakert Airport, operationLimitationReason, political issues]
-
A.
reasonForPerformanceLimitation
chosen
Indicates that one factor serves as the cause or explanation for why a performance limitation occurs.
-
B.
oversLimit
Indicates that an entity exceeds a specified limit, threshold, or allowed maximum.
-
C.
rateConstraint
Indicates a limitation or bound on the rate at which a process, transaction, or interaction is allowed to occur.
-
D.
hasLimitation
Indicates that an entity is subject to a constraint, restriction, or boundary that limits its scope, capability, or applicability.
-
E.
hasIntegrationLimitType
Indicates the type or nature of the integration limit applied in a given relationship or process.
- 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_69f0bd48691081908cecad39bac591e0 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69ff17be6ad48190963206f2619b1b28 |
completed | May 9, 2026, 11:17 a.m. |
| PD | Predicate disambiguation | batch_69ff1724ba24819092c928fcbcb286ec |
completed | May 9, 2026, 11:14 a.m. |
Created at: April 28, 2026, 5:08 p.m.