Triple
T24924152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jan Mayensfield airstrip |
E618803
|
entity |
| Predicate | publicScheduledService |
P159705
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Jan Mayensfield airstrip, publicScheduledService, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicScheduledService Context triple: [Jan Mayensfield airstrip, publicScheduledService, no]
-
A.
plannedService
Indicates that a service is scheduled or intended to be provided, but has not yet occurred.
-
B.
scheduledServiceType
Indicates the type or category of service that has been scheduled between entities (e.g., maintenance, appointment, or delivery).
-
C.
scheduledAs
Indicates that one entity is assigned or arranged to occur or function in the role, time, or capacity specified by another entity within a schedule.
-
D.
scheduledAfter
Indicates that one event or action is planned to occur later in time than another in a defined schedule or sequence.
-
E.
parallelService
Indicates that two or more services operate concurrently or in parallel rather than sequentially.
- F. None of above. chosen
Provenance (4 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_69e2fab9edd88190b86004a78a28bc20 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f5f7a205688190b8f36bff5013247c |
completed | May 2, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
| PDg | Predicate description generation | batch_69f5f6b32a8881909baa0db57b80d56a |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 18, 2026, 5:29 a.m.