Triple
T24229344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austfonna |
E601682
|
entity |
| Predicate | hasNotableSurgeEvent |
P22468
|
FINISHED |
| Object | early 2010s |
—
|
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 2010s | Statement: [Austfonna, hasNotableSurgeEvent, early 2010s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableSurgeEvent Context triple: [Austfonna, hasNotableSurgeEvent, early 2010s]
-
A.
hasNotableIncident
Indicates that an entity is associated with a significant or noteworthy event, occurrence, or incident.
-
B.
hasNotableRapid
Indicates that an entity possesses a rapid (a fast-flowing section of a river or stream) that is considered notable or significant.
-
C.
hadEvent
chosen
Indicates that an entity experienced, hosted, or was associated with a specific event at some point in time.
-
D.
hasNotableEventName
Indicates that an entity is associated with a notable event identified by a specific name.
-
E.
hasNotableNumber
Indicates that an entity is associated with a specific number that is considered significant, distinctive, or noteworthy in some context.
- 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_69e29538aafc8190a2386fdebbd1393b |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f287e214e88190bf6d5b0f5f489f73 |
completed | April 29, 2026, 10:36 p.m. |
| PD | Predicate disambiguation | batch_69f1c448abec8190b87cbf9ed419a309 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:01 a.m.