Triple
T3026804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gerardus Mercator |
E82793
|
entity |
| Predicate | purposeOfWork |
P44716
|
FINISHED |
| Object | improving nautical navigation |
—
|
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: improving nautical navigation | Statement: [Gerardus Mercator, purposeOfWork, improving nautical navigation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: purposeOfWork Context triple: [Gerardus Mercator, purposeOfWork, improving nautical navigation]
-
A.
settingOfWork
Indicates the place, time, or environment in which a creative work’s narrative or events are situated.
-
B.
subjectOfWork
Indicates that one entity is the main topic, focus, or theme that a particular work (such as a book, article, or artwork) is about.
-
C.
typeOfWork
Indicates the kind or category of work associated with or performed by an entity.
-
D.
workRelatedTo
Indicates a relationship where one entity’s work, tasks, or professional activities are connected, associated, or relevant to those of another entity.
-
E.
workDescribedIn
Indicates that a work (such as a publication or document) provides a description or account of the referenced 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_69ad8b21a62881908ec5dd4fba4a187c |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9abd85348190aba9e40658697665 |
completed | March 8, 2026, 3:50 p.m. |
| PD | Predicate disambiguation | batch_69ad961c430c8190ac48f2e3c7e7c649 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f6af3881909f4547967384114c |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 3 p.m.