Triple
T17298433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George Burns |
E419971
|
entity |
| Predicate | routeSpecialization |
P126877
|
FINISHED |
| Object | transatlantic routes |
—
|
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: transatlantic routes | Statement: [George Burns, routeSpecialization, transatlantic routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routeSpecialization Context triple: [George Burns, routeSpecialization, transatlantic routes]
-
A.
routeTypeAccessed
Indicates that a particular type of route has been accessed or used in some context.
-
B.
routeTargeted
Indicates that a route is specifically directed toward or intended to reach a particular target entity or destination.
-
C.
routingBasis
Indicates the principle or criterion used to determine how something is directed, routed, or assigned among possible paths or destinations.
-
D.
routeMayInclude
Indicates that a given route can optionally pass through, contain, or involve a specified segment, location, or element as part of its path.
-
E.
routeRole
Indicates the specific functional role or purpose that an entity has within a particular route or path.
- 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_69d886db32608190a61e18862c5a8af6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e438f82788819088ea796850552297 |
completed | April 19, 2026, 2:07 a.m. |
| PD | Predicate disambiguation | batch_69e3b0118ad08190b119cd219c68ba67 |
completed | April 18, 2026, 4:23 p.m. |
| PDg | Predicate description generation | batch_69e3b2a225b08190a50f984caa6513b9 |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:41 a.m.