Triple
T37620433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Howard's Rock |
E936051
|
entity |
| Predicate | vandalismResult |
P175461
|
FINISHED |
| Object | portion of the rock was broken off |
—
|
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: portion of the rock was broken off | Statement: [Howard's Rock, vandalismResult, portion of the rock was broken off]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vandalismResult Context triple: [Howard's Rock, vandalismResult, portion of the rock was broken off]
-
A.
wasVandalized
chosen
Indicates that an entity has been deliberately damaged, defaced, or destroyed through an act of vandalism.
-
B.
violationOf
Indicates that one entity breaches, disobeys, or infringes upon a rule, law, agreement, or right associated with another entity.
-
C.
damagedWorkBy
Indicates that one entity has caused harm, impairment, or destruction to a work created by another entity.
-
D.
defacedWith
Indicates that one entity has been damaged, marred, or vandalized using another entity as the means or material of defacement.
-
E.
demolishedAsResultOf
Indicates that one entity was demolished as a direct consequence or outcome of another event, action, or condition.
- 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_69f76ed16b748190ad6add183b1be688 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb084760c8190a1554985d3c3cb7a |
completed | May 6, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69fbadf3cb548190ba3b7514f76b790a |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:18 p.m.