Triple
T27769723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SouthJet Airlines |
E701708
|
entity |
| Predicate | operatesFictionalService |
P61295
|
FINISHED |
| Object | passenger air transport |
—
|
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: passenger air transport | Statement: [SouthJet Airlines, operatesFictionalService, passenger air transport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesFictionalService Context triple: [SouthJet Airlines, operatesFictionalService, passenger air transport]
-
A.
fictionalService
chosen
Indicates that one entity provides or is associated with an imagined or non-real service in relation to another entity.
-
B.
operatesService
Indicates that an agent runs, manages, or provides a particular service.
-
C.
operatesServiceTo
Indicates that one entity runs or provides a transportation or service route to another entity or location.
-
D.
operatesOnlineService
Indicates that an entity runs or manages an online service or platform for others to use.
-
E.
serviceOf
Indicates that one entity performs, provides, or fulfills a function or duty on behalf of 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_69ef6a52fa708190934a32308d2c92dc |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69fe08d2b2e48190ac7be6d62d4a44a3 |
completed | May 8, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69fe06cd3af08190ae25de0dc0cdd573 |
completed | May 8, 2026, 3:52 p.m. |
Created at: April 27, 2026, 4:34 p.m.