Triple
T21557901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rayak |
E531939
|
entity |
| Predicate | airBaseStatus |
P82902
|
FINISHED |
| Object | active military air base |
—
|
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: active military air base | Statement: [Rayak, airBaseStatus, active military air base]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airBaseStatus Context triple: [Rayak, airBaseStatus, active military air base]
-
A.
airBaseOperator
Indicates that one entity operates, manages, or is responsible for running an air base used for aviation activities.
-
B.
airportStatus
Indicates the current operational condition or state of an airport (e.g., open, closed, delayed, restricted).
-
C.
militaryBaseStatus
chosen
Indicates the operational condition or readiness state of a military base at a given time.
-
D.
isAirBase
Indicates that the subject entity functions as a military air base, i.e., a facility used for operating, housing, and supporting aircraft and related activities.
-
E.
aircraftStatus
Indicates the current operational condition or state of an aircraft (e.g., active, grounded, in maintenance, or decommissioned).
- 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_69e0c460232c81908de2c3819d17c00e |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eed2e14af88190bc70b4d0f3453aac |
completed | April 27, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69e6320766308190ba5dca2f7c826aa4 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:29 p.m.