Triple
T3471927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warrenton–Fauquier Airport |
E73279
|
entity |
| Predicate | hasMaintenanceServices |
P45840
|
FINISHED |
| Object | aircraft maintenance |
—
|
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: aircraft maintenance | Statement: [Warrenton–Fauquier Airport, hasMaintenanceServices, aircraft maintenance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaintenanceServices Context triple: [Warrenton–Fauquier Airport, hasMaintenanceServices, aircraft maintenance]
-
A.
hasMaintenanceService
chosen
Indicates that an entity receives or is covered by a maintenance service provided by another entity.
-
B.
hasSupportService
Indicates that one entity provides or is associated with a support-related service for another entity.
-
C.
hasServiceChief
Indicates that one entity serves as the chief or head responsible for overseeing the services of another entity.
-
D.
hasDailyService
Indicates that a service or operation occurs every day on a regular, scheduled basis.
-
E.
hasServiceTo
Indicates that one entity provides, offers, or operates a service for or directed toward another entity.
- 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_69ad85b2fed48190948c8765e453d270 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbb3cc8488190b97c732e3f600a90 |
completed | March 8, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69adae07802c8190919c49b0e65b2797 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:17 p.m.