Triple
T34308191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paper Log House |
E880367
|
entity |
| Predicate | deployedAfter |
P10187
|
FINISHED |
| Object | Great Hanshin earthquake |
—
|
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: Great Hanshin earthquake | Statement: [Paper Log House, deployedAfter, Great Hanshin earthquake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deployedAfter Context triple: [Paper Log House, deployedAfter, Great Hanshin earthquake]
-
A.
deployedSince
Indicates that an entity has been deployed starting from a specific point in time and has remained in that deployed state since then.
-
B.
deployedFor
Indicates that one entity is deployed or put into operational use to serve, support, or act on behalf of another entity.
-
C.
laterDeployedIn
chosen
Indicates that one entity was deployed or put into operation in a particular context, location, or system at a later time than another.
-
D.
deployedTo
Indicates that something (such as a resource, application, or unit) has been placed, installed, or made operational in a specific target environment or location.
-
E.
deploymentTime
Indicates the point in time at which something is deployed, initiated, or put into operation.
- 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_69f349b8bb6c8190ad12a7957a574f04 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f717836f0c8190b4a397bbac37dd09 |
completed | May 3, 2026, 9:38 a.m. |
| PD | Predicate disambiguation | batch_69f7127a2ff08190b77d00963c9df621 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:57 a.m.