Triple
T13278813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | N106US |
E316262
|
entity |
| Predicate | postEventStatus |
P109295
|
FINISHED |
| Object | substantially damaged |
—
|
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: substantially damaged | Statement: [N106US, postEventStatus, substantially damaged]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postEventStatus Context triple: [N106US, postEventStatus, substantially damaged]
-
A.
postAcquisitionStatus
Indicates the condition or state of an entity after it has been acquired by another party.
-
B.
publishedEvent
Indicates that an entity has formally released or made an event publicly available or announced.
-
C.
postMergerStatus
Indicates the status or condition of an entity following the completion of a merger.
-
D.
campaignStatus
Indicates the current state or phase of a campaign within its lifecycle (e.g., planned, active, paused, or completed).
-
E.
postRevoltStatus
Indicates the condition or state of an entity after a revolt or uprising has occurred.
- 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_69d806b349908190a9a61dd9323bf153 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6535688190a5a4549b7be2d611 |
completed | April 11, 2026, 12:01 a.m. |
| PDg | Predicate description generation | batch_69d99cf7f9c48190a6a4f452b4a2aefa |
completed | April 11, 2026, 12:59 a.m. |
Created at: April 9, 2026, 9:26 p.m.