Triple
T37164046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISDB |
E920747
|
entity |
| Predicate | firstCountryOfDeployment |
P124773
|
FINISHED |
| Object | Japan |
E174
|
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: Japan | Statement: [ISDB, firstCountryOfDeployment, Japan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstCountryOfDeployment Context triple: [ISDB, firstCountryOfDeployment, Japan]
-
A.
countryOfFirstDeployment
chosen
Indicates the country where something (such as equipment, technology, or a system) was first put into operational use or service.
-
B.
countryOfDeployment
Indicates the country where an entity (such as a person, unit, or asset) is currently or was assigned, stationed, or operating.
-
C.
firstCombatOperation
Indicates that the referenced combat operation is the earliest or initial combat action undertaken by the entity in question.
-
D.
firstCombatUseLocation
Indicates the location where something (typically a weapon, system, or tactic) was used in combat for the first time.
-
E.
firstOperationalUse
Indicates the point in time or context when something is used operationally for the very first time.
- 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_69f76ea0429081908c711b55599eac3c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a402bae19848190b1de3481dfd22b00 |
completed | June 27, 2026, 7:59 p.m. |
| PD | Predicate disambiguation | batch_6a037a11efc08190bb7cacc1325b4dc6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:15 p.m.