Triple
T36273670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2023 Marrakesh–Safi earthquake |
E892742
|
entity |
| Predicate | stronglyFeltIn |
P31091
|
FINISHED |
| Object | Casablanca |
—
|
NE NERFINISHED |
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: Casablanca | Statement: [2023 Marrakesh–Safi earthquake, stronglyFeltIn, Casablanca]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stronglyFeltIn Context triple: [2023 Marrakesh–Safi earthquake, stronglyFeltIn, Casablanca]
-
A.
feltIn
chosen
Indicates that a sensation, emotion, or effect is experienced within a particular location, context, or entity.
-
B.
strongShakingAlsoFeltIn
Indicates that intense shaking at one location was also experienced in another location.
-
C.
strongestSupportRegion
Indicates the region where an entity receives its highest level of support compared to all other regions.
-
D.
locationGaveRiseTo
Indicates that a particular location is the origin or source from which something (such as an event, movement, phenomenon, or entity) emerged or developed.
-
E.
regionWithStrongBlocSupport
Indicates that a geographic region exhibits notably high or concentrated support for a particular political bloc or alliance.
- 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_69f76e488f34819083e254dbe288c27a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7ba6d06f48190a71b5a2f19e2232f |
completed | May 3, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a4aad48190a62e41c5e39339d9 |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:09 p.m.