Triple
T15453000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Harrison |
E371696
|
entity |
| Predicate | problemSolved |
P22418
|
FINISHED |
| Object | practical determination of longitude at sea |
—
|
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: practical determination of longitude at sea | Statement: [John Harrison, problemSolved, practical determination of longitude at sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: problemSolved Context triple: [John Harrison, problemSolved, practical determination of longitude at sea]
-
A.
problemTypeSolved
Indicates that a given problem has been successfully solved or resolved by a particular entity or method.
-
B.
solved
chosen
Indicates that one entity has successfully found a solution or answer to a problem, task, or challenge involving another entity.
-
C.
numberOfProblems
Indicates the quantity or count of problems associated with a given entity or situation.
-
D.
problemType
Indicates the specific category or classification of a problem within a defined problem space or system.
-
E.
problems
Indicates that one entity has issues, difficulties, or complications associated with or caused by 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_69d85cc8bd308190886949510b42e764 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f131b1481909ff099c3b844ee07 |
completed | April 16, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69ded28276f481908c2038bb301e57cf |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:30 a.m.