Triple
T13456934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brawley Seismic Zone |
E311259
|
entity |
| Predicate | hasSeismicBehavior |
P109585
|
FINISHED |
| Object | swarm-like activity |
—
|
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: swarm-like activity | Statement: [Brawley Seismic Zone, hasSeismicBehavior, swarm-like activity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeismicBehavior Context triple: [Brawley Seismic Zone, hasSeismicBehavior, swarm-like activity]
-
A.
earthquakeResistance
Indicates how well an entity can withstand or remain functional during an earthquake without significant damage.
-
B.
seismicSignificance
Indicates the degree to which something is relevant, influential, or important in the context of seismic activity or earthquake-related phenomena.
-
C.
hasEarthquakes
Indicates that the specified location or region experiences one or more earthquakes.
-
D.
seismicDesign
Indicates that an entity is designed or engineered to withstand seismic activity or earthquake-related forces.
-
E.
seismicSafetyConcernsIdentified
Indicates that potential risks or issues related to seismic safety have been detected or recognized.
- 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_69d806a938b8819097ec43a2229fc7f9 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf0a75008190a508060c85f73604 |
completed | April 12, 2026, 2:41 p.m. |
| PD | Predicate disambiguation | batch_69d9a03ce03481908c61094f0cc0c158 |
completed | April 11, 2026, 1:13 a.m. |
| PDg | Predicate description generation | batch_69dadce235f88190a6433395d2969811 |
completed | April 11, 2026, 11:44 p.m. |
Created at: April 9, 2026, 9:41 p.m.