Triple
T31660552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avonside |
E807988
|
entity |
| Predicate | hasPostEarthquakeIssue |
P196985
|
FINISHED |
| Object | liquefaction damage |
—
|
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: liquefaction damage | Statement: [Avonside, hasPostEarthquakeIssue, liquefaction damage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPostEarthquakeIssue Context triple: [Avonside, hasPostEarthquakeIssue, liquefaction damage]
-
A.
statusAfter2015Earthquake
Indicates the condition or state of something following the 2015 earthquake.
-
B.
statusAfter2011Earthquake
Indicates the condition or state of something following the 2011 earthquake.
-
C.
hasEarthquakes
Indicates that the specified location or region experiences one or more earthquakes.
-
D.
facedMajorEarthquake
Indicates that an entity has experienced or been subjected to a significant or severe earthquake event.
-
E.
hasEarlyEarthquakesReportedSince
Indicates that earlier-than-expected earthquakes have been reported starting from a specified point in time.
- 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_69f348daf95c81908b4c985b7ddcd0b3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe72dca2f08190beff17de3d2aada6 |
completed | May 8, 2026, 11:33 p.m. |
| PD | Predicate disambiguation | batch_69fe70bca8d08190b810e1e616ceac44 |
completed | May 8, 2026, 11:24 p.m. |
| PDg | Predicate description generation | batch_69fe72db8810819089e397961b8ead7a |
completed | May 8, 2026, 11:33 p.m. |
Created at: April 30, 2026, 10:57 p.m.