Triple
T34439791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SQ22 |
E884064
|
entity |
| Predicate | returnRoute |
P188464
|
FINISHED |
| Object | New York to Singapore |
—
|
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: New York to Singapore | Statement: [SQ22, returnRoute, New York to Singapore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnRoute Context triple: [SQ22, returnRoute, New York to Singapore]
-
A.
originalRoute
Indicates that one route is the initial or primary path from which another route is derived, modified, or compared.
-
B.
previousRoute
Indicates that one route directly precedes another in an ordered sequence of routes.
-
C.
returnDirection
Indicates the direction in which something goes back or is sent back to its point of origin or previous location.
-
D.
nextRoute
Indicates that one route directly follows another in a defined sequence or ordering of routes.
-
E.
route
Indicates that one entity serves as a path or course used to travel or move between locations associated with another entity.
- 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_69f349c548d88190978e2a82502c03d0 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69fba789c1188190973a919bfe2871f3 |
completed | May 6, 2026, 8:41 p.m. |
Created at: May 1, 2026, 2 a.m.