Triple
T1299735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jan Mayen |
E27733
|
entity |
| Predicate | hasDiscoveryPeriod |
P26767
|
FINISHED |
| Object | early 17th century |
—
|
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: early 17th century | Statement: [Jan Mayen, hasDiscoveryPeriod, early 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDiscoveryPeriod Context triple: [Jan Mayen, hasDiscoveryPeriod, early 17th century]
-
A.
hasDiscoveryStatus
Indicates the current state or phase of discovery or identification associated with an entity.
-
B.
discoveredSince
Indicates that one entity has been discovered starting from, or at some point after, a specified time or event associated with another entity.
-
C.
hasAwardPeriod
Indicates the time span or date range during which an award is valid, active, or applicable.
-
D.
wasDiscoveredAt
Indicates that an entity was found, identified, or uncovered at a specific place or during a particular event or context.
-
E.
completedWithDiscoveryOf
Indicates that an action, process, or event was brought to completion as a direct result of a particular discovery.
- 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_69a496d6682881909ba658f1c1e0e2b0 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c11314a48190ab4efb8b1acdce50 |
completed | March 1, 2026, 10:43 p.m. |
| PD | Predicate disambiguation | batch_69a4bee8544c8190874efd9bae9bccf9 |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4bf60545c8190901ccfb2cb7c4b41 |
completed | March 1, 2026, 10:36 p.m. |
Created at: March 1, 2026, 7:51 p.m.