Triple
T20365680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suribachi-yama |
E496900
|
entity |
| Predicate | wasHeavilyFortified |
P11105
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Suribachi-yama, wasHeavilyFortified, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasHeavilyFortified Context triple: [Suribachi-yama, wasHeavilyFortified, true]
-
A.
wasFortifiedBy
Indicates that a place or structure received defensive strengthening or fortification through the actions or resources of a specified agent or entity.
-
B.
isFortifiedWith
Indicates that one entity has been strengthened, enriched, or supplemented by the addition of another entity.
-
C.
fortifiedIn
Indicates that one entity has been strengthened, reinforced, or protected within or by another entity (such as a structure, location, or medium).
-
D.
fortifiedWith
Indicates that something has been strengthened, enhanced, or reinforced by the addition of a specified substance, feature, or element.
-
E.
isFortifiedCity
chosen
Indicates that a city is strengthened with defensive structures or fortifications, such as walls, ramparts, or similar protective works.
- 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_69e0b4a4f9b081908a5a021919c21ccb |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67871bfdc8190948c46497cd675c9 |
completed | April 20, 2026, 7:03 p.m. |
| PD | Predicate disambiguation | batch_69e57648be3c81908256838228cabf5c |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:26 a.m.