Triple
T28429095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gumaca |
E715068
|
entity |
| Predicate | hasDefenseStructure |
P22477
|
FINISHED |
| Object | stone fortress |
—
|
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: stone fortress | Statement: [Gumaca, hasDefenseStructure, stone fortress]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDefenseStructure Context triple: [Gumaca, hasDefenseStructure, stone fortress]
-
A.
shareDefenseStructure
Indicates that two or more entities utilize or are protected by the same defensive structure or system.
-
B.
defensiveStructure
Indicates a relationship where one entity functions as a structure built or used to protect, defend, or fortify another entity or area.
-
C.
hasFortifications
chosen
Indicates that one entity possesses or is equipped with defensive structures or fortification works associated with it.
-
D.
isFortifiedStructureOf
Indicates that one entity is a defensive or fortified structure that protects, encloses, or is associated with another entity.
-
E.
fortressDefended
Indicates that a fortress is actively protected against threats or attacks by some defending force.
- 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_69efd6b253888190b3c7222ed6a403a8 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: April 28, 2026, 1:38 a.m.