Triple
T1007539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1883 eruption of Krakatoa |
E21747
|
entity |
| Predicate | soundHeardDistanceApproximate |
P23533
|
FINISHED |
| Object | 3000 miles |
—
|
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: 3000 miles | Statement: [1883 eruption of Krakatoa, soundHeardDistanceApproximate, 3000 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: soundHeardDistanceApproximate Context triple: [1883 eruption of Krakatoa, soundHeardDistanceApproximate, 3000 miles]
-
A.
canHear
Indicates that one entity is able to perceive sounds produced by another entity.
-
B.
soundCharacter
Indicates a relationship where one entity specifies the quality, style, or distinguishing characteristics of a sound produced or perceived in another entity.
-
C.
hasSound
Indicates that an entity produces, emits, or is associated with a particular sound.
-
D.
mayHear
Indicates that one entity is permitted or able to hear sounds, speech, or audio produced by another entity.
-
E.
hasHeavierSoundThan
Indicates that one entity produces or is associated with a sound that is sonically heavier, more intense, or more forceful than that of 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_69a493c53e648190ae8cb76c433fd9a7 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b7f4c66c8190b6098fb72c1465a3 |
completed | March 1, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69a4b7203124819091de68cba5f731c1 |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4b7f2d1b081908eb2df54e91c8c1d |
completed | March 1, 2026, 10:04 p.m. |
Created at: March 1, 2026, 7:41 p.m.