Triple
T32065710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warmia |
E818873
|
entity |
| Predicate | CopernicusWorkedIn |
P173179
|
FINISHED |
| Object | Frombork |
—
|
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: Frombork | Statement: [Warmia, CopernicusWorkedIn, Frombork]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: CopernicusWorkedIn Context triple: [Warmia, CopernicusWorkedIn, Frombork]
-
A.
GalileoGalileiRole
Indicates the role, position, or capacity in which Galileo Galilei is related to or involved with another entity or activity.
-
B.
documentedInWorkByTychoBrahe
Indicates that the subject was recorded or described in a scholarly or observational work authored by Tycho Brahe.
-
C.
discovererLocation
Indicates the place where the person or entity that discovered something was located at the time of the discovery.
-
D.
firstTelescopicObservationBy
Indicates that the object was the target of the earliest known telescopic observation made by the specified observer.
-
E.
roleInHistoryOfAstronomy
Indicates the role or contribution an entity has had in the development or progression of the field of astronomy over time.
- 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_69f348fecc088190af1470afe5a969f0 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b51cc924819080cd8f31a84f4b44 |
completed | May 3, 2026, 2:38 a.m. |
| PD | Predicate disambiguation | batch_69f6b154b3dc819087115f5f63f7b00f |
completed | May 3, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69f6b267b90c8190807208cadce5ae8d |
completed | May 3, 2026, 2:26 a.m. |
Created at: May 1, 2026, 12:22 a.m.