Triple
T16491047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gunnbjörn Ulfsson |
E400567
|
entity |
| Predicate | discoveryClaim |
P123724
|
FINISHED |
| Object | first European sighting of Greenland |
—
|
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: first European sighting of Greenland | Statement: [Gunnbjörn Ulfsson, discoveryClaim, first European sighting of Greenland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discoveryClaim Context triple: [Gunnbjörn Ulfsson, discoveryClaim, first European sighting of Greenland]
-
A.
recognizedClaimOf
Indicates that one entity formally acknowledges the validity or legitimacy of a claim made by another entity.
-
B.
scopeClaim
Indicates that a claim or statement applies within a specified scope, context, or boundary.
-
C.
discoveryConfirmed
Indicates that a previously identified potential discovery has been verified as valid or true.
-
D.
discoveryConfirmedBy
Indicates that a discovery has been validated or corroborated by a particular source, authority, or piece of evidence.
-
E.
discoveredAs
Indicates that one entity was first identified, found, or recognized in the role or form specified by another 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_69d883813098819084f5409539723b59 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e300a248190a3d4ca96a0a176cf |
completed | April 18, 2026, 7:09 a.m. |
| PD | Predicate disambiguation | batch_69e296902d6c8190884ddb612b8c5b36 |
completed | April 17, 2026, 8:22 p.m. |
| PDg | Predicate description generation | batch_69e2d7f97e548190a474691a152bd8e8 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 10, 2026, 5:13 a.m.