Triple
T5785158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sir Hans Sloane |
E128251
|
entity |
| Predicate | traveledFor |
P65824
|
FINISHED |
| Object | medical practice in Jamaica |
—
|
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: medical practice in Jamaica | Statement: [Sir Hans Sloane, traveledFor, medical practice in Jamaica]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traveledFor Context triple: [Sir Hans Sloane, traveledFor, medical practice in Jamaica]
-
A.
distanceTraveled
Indicates the total length of the path an entity has moved over a period of time or between two points.
-
B.
travelsThrough
Indicates that something moves along, passes across, or is routed via a particular path, medium, or location.
-
C.
wentToDistance
Indicates that an entity traveled to or reached a specified distance from a reference point.
-
D.
involvedTravelBetween
Indicates a relationship where an entity participates in or is associated with travel occurring between two specified locations.
-
E.
trailDistanceApprox
Indicates that the distance along a trail between two locations is approximately a specified value, allowing for some margin of error.
- 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_69c0084450048190bc647b649a05136b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02a1af0ec8190a47be1b7e7b5cda7 |
completed | March 22, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69c021d2cd608190b98a7e3aa7001d27 |
completed | March 22, 2026, 5:07 p.m. |
| PDg | Predicate description generation | batch_69c024861bc88190a17782c1982fbb3e |
completed | March 22, 2026, 5:19 p.m. |
Created at: March 22, 2026, 3:51 p.m.