Triple
T28984478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Storsjöodjuret |
E734640
|
entity |
| Predicate | hasSightingsReportedSince |
P114231
|
FINISHED |
| Object | 19th 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: 19th century | Statement: [Storsjöodjuret, hasSightingsReportedSince, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSightingsReportedSince Context triple: [Storsjöodjuret, hasSightingsReportedSince, 19th century]
-
A.
lastKnownWildSightingYear
Indicates the calendar year in which the entity was most recently observed living in the wild.
-
B.
possibleSightings
chosen
Indicates that there are reported or potential observations of one entity by another or at a particular place or time.
-
C.
hasEvidenceOfActivitySince
Indicates that there is evidence showing an entity has been active or engaged in some activity from a specified point in time onward.
-
D.
sightingState
Indicates the current status or condition of a reported sighting within its tracking or verification process.
-
E.
isReportedAt
Indicates that an event, fact, or occurrence is documented or made known at a particular time, place, or reporting source.
- 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_69f05b0dd9b481908b7901e1c95ff6b2 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
Created at: April 28, 2026, 9:13 a.m.