Triple
T5837932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gjøa |
E129518
|
entity |
| Predicate | scientificWork |
P11773
|
FINISHED |
| Object | magnetic North Pole observations |
—
|
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: magnetic North Pole observations | Statement: [Gjøa, scientificWork, magnetic North Pole observations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scientificWork Context triple: [Gjøa, scientificWork, magnetic North Pole observations]
-
A.
scholarlyWork
Indicates a relationship where an entity is a formal academic or research work produced, published, or recognized within a scholarly context.
-
B.
researchContribution
chosen
Indicates that an entity has produced or participated in creating new knowledge, findings, or innovations within a research context.
-
C.
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.
-
D.
publicationBody
Indicates the organization or entity that serves as the publishing body responsible for issuing the referenced work.
-
E.
publicationType
Indicates the specific category or format of a published work that characterizes how it is issued or presented.
- 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_69c0084af79c81908af128ccc29983d0 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c044ab0a048190b84be40fb13c0f50 |
completed | March 22, 2026, 7:36 p.m. |
| PD | Predicate disambiguation | batch_69c03341e5888190a5f219b6f92cb161 |
completed | March 22, 2026, 6:21 p.m. |
Created at: March 22, 2026, 3:54 p.m.