Triple
T34308190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paper Log House |
E880367
|
entity |
| Predicate | firstDeployedLocation |
P40892
|
FINISHED |
| Object | Kobe, Japan |
E499546
|
NE 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: Kobe, Japan | Statement: [Paper Log House, firstDeployedLocation, Kobe, Japan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstDeployedLocation Context triple: [Paper Log House, firstDeployedLocation, Kobe, Japan]
-
A.
firstDeployedIn
chosen
Indicates the time or place where something (such as a system, product, or technology) was initially put into operational use or service.
-
B.
firstDeployed
Indicates the time or event when something (such as a system, product, or resource) was initially put into active use or operation.
-
C.
firstDeployedAt
Indicates the date and time when an entity was initially put into use or made operational.
-
D.
firstDeployedFor
Indicates that an entity was initially deployed or put into operational use specifically for another entity (such as a project, mission, or organization).
-
E.
countryOfFirstDeployment
Indicates the country where something (such as equipment, technology, or a system) was first put into operational use or service.
- F. None of above.
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_69f349b8bb6c8190ad12a7957a574f04 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36e63d88d481908f1426ea115d03a6 |
completed | June 20, 2026, 7:13 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:57 a.m.