Triple
T35599300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John George Phillips |
E1028722
|
entity |
| Predicate | workedOnRoute |
P21808
|
FINISHED |
| Object | North Atlantic shipping route |
—
|
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: North Atlantic shipping route | Statement: [John George Phillips, workedOnRoute, North Atlantic shipping route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workedOnRoute Context triple: [John George Phillips, workedOnRoute, North Atlantic shipping route]
-
A.
operatedOnRoute
chosen
Indicates that a transportation service or vehicle was active and provided service along a specified route.
-
B.
workedOnTour
Indicates that an entity participated in or contributed work to a particular tour.
-
C.
workOn
Indicates that an agent is actively engaged in performing tasks or making progress on a particular project, object, or assignment.
-
D.
hadRoute
Indicates that an entity (such as a service, vehicle, or system) followed, operated on, or was associated with a specific route.
-
E.
workedUnder
Indicates that one entity was hierarchically subordinate to and performed work under the supervision or authority 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_69f76e0598dc8190a6a093e904b9aa70 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79ec355048190af30123ceb6efa2b |
completed | May 3, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:05 p.m.