Triple
T34439801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SQ22 |
E884064
|
entity |
| Predicate | routeMarketingName |
P24366
|
FINISHED |
| Object | Singapore–New York nonstop |
—
|
NE NERFINISHED |
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: Singapore–New York nonstop | Statement: [SQ22, routeMarketingName, Singapore–New York nonstop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routeMarketingName Context triple: [SQ22, routeMarketingName, Singapore–New York nonstop]
-
A.
resolutionMarketingName
Indicates the marketed or consumer-facing name used to describe a product’s resolution.
-
B.
marketingNameOf
chosen
Indicates that one entity is the marketing or brand name used to promote or refer to another entity.
-
C.
primaryMarketedRouteName
Indicates the main route or method by which a product is marketed or delivered to its intended users.
-
D.
routeDesignationOf
Indicates that one entity is the official route number, code, or designation assigned to another entity representing a transportation route.
-
E.
routeSymbol
Indicates that a particular symbol or code is used to represent or identify a specific route.
- 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_69f349c548d88190978e2a82502c03d0 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71fb1ab3881908e2f7c0e6f23db49 |
completed | May 3, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f71cc6397881909aaad37a9daa8a7e |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2 a.m.