Triple
T9949702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Flood of 1879 |
E195297
|
entity |
| Predicate | survivingBuildings |
P6429
|
FINISHED |
| Object | fewer than 300 houses |
—
|
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: fewer than 300 houses | Statement: [Great Flood of 1879, survivingBuildings, fewer than 300 houses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: survivingBuildings Context triple: [Great Flood of 1879, survivingBuildings, fewer than 300 houses]
-
A.
survivingStructure
chosen
Indicates that a structure continues to exist or remain intact after a potentially destructive event or over a significant period of time.
-
B.
survivorsBuilt
Indicates that the entities identified as survivors constructed, created, or established the associated object or structure.
-
C.
survivingFrom
Indicates that one entity continues to live, exist, or remain after another related entity has ended, disappeared, or ceased to exist.
-
D.
buildingsDestroyed
Indicates that one or more buildings have been damaged to the point of destruction as a result of some event or action.
-
E.
survivesIn
Indicates that an entity remains alive, functional, or intact within a specified environment, condition, or context.
- 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_69ca82e96a108190932bd1fc4acd73a0 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb65a4e6c8190968192a24aad1b7d |
completed | April 2, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69cd1d97c44081908730071269f07712 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:45 p.m.