Triple
T832247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kīlauea |
E17990
|
entity |
| Predicate | hasContinuousActivitySince |
P19818
|
FINISHED |
| Object | early 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: early 19th century | Statement: [Kīlauea, hasContinuousActivitySince, early 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasContinuousActivitySince Context triple: [Kīlauea, hasContinuousActivitySince, early 19th century]
-
A.
hasActivityStatus
Indicates the current state or condition of an activity, such as whether it is planned, ongoing, completed, or cancelled.
-
B.
hasActivityIn
Indicates that an entity engages in or performs a particular activity within a specified context, location, or domain.
-
C.
hasKeyActivity
Indicates that an entity is associated with or performs a primary or central activity.
-
D.
currentStatusSince
chosen
Indicates the point in time since which an entity has held its current status or state.
-
E.
hasActivityAtIssue
Indicates that an entity is associated with a specific activity that is currently under consideration, discussion, or dispute.
- 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_69a4937c9c188190aaa216f6b466f452 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4abb647988190950e1790bcfa60a5 |
completed | March 1, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69a4aa7b3d2481909199f7c9f305bdfe |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.