Triple
T4526414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nadi–Auckland |
E106188
|
entity |
| Predicate | typicalServiceType |
P849
|
FINISHED |
| Object | scheduled passenger flight |
—
|
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: scheduled passenger flight | Statement: [Nadi–Auckland, typicalServiceType, scheduled passenger flight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalServiceType Context triple: [Nadi–Auckland, typicalServiceType, scheduled passenger flight]
-
A.
notableServiceType
Indicates that the subject is associated with a particular type or category of service that is especially notable or significant.
-
B.
serviceOf
Indicates that one entity performs, provides, or fulfills a function or duty on behalf of another entity.
-
C.
hasServiceType
chosen
Indicates that an entity is associated with or categorized by a particular type of service.
-
D.
serviceFor
Indicates that one entity provides a service or performs functions on behalf of another entity.
-
E.
serviceIn
Indicates that one entity serves, operates, or performs its function within the context, scope, or domain 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_69bd43f3d6e08190a91824f833d51bbe |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd57760f4481908f69ce82be63d7f8 |
completed | March 20, 2026, 2:19 p.m. |
| PD | Predicate disambiguation | batch_69bd521cf77c819083852de3094d1377 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:03 p.m.