Triple
T13089699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Juan Hill |
E310426
|
entity |
| Predicate | defensiveStructures |
P66714
|
FINISHED |
| Object | Spanish entrenchments |
—
|
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: Spanish entrenchments | Statement: [San Juan Hill, defensiveStructures, Spanish entrenchments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defensiveStructures Context triple: [San Juan Hill, defensiveStructures, Spanish entrenchments]
-
A.
defensiveStructure
Indicates a relationship where one entity functions as a structure built or used to protect, defend, or fortify another entity or area.
-
B.
opposedFortification
Indicates that one entity actively resisted, challenged, or worked against the strengthening or fortifying of another entity or location.
-
C.
fortifiedBuilding
Indicates that a building is strengthened or reinforced for defense against attacks or intrusions.
-
D.
militaryArchitecture
Indicates a relationship where something is designed, built, or characterized specifically for military defensive or fortification purposes.
-
E.
usedFortificationsAt
chosen
Indicates that an entity employed or deployed specific fortifications in a particular context, such as a battle, campaign, or defensive situation.
- 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_69d806a733548190989cfd4ce981ca33 |
completed | April 9, 2026, 8:05 p.m. |
| NER | Named-entity recognition | batch_69d98138a1d481908a139f2f67eb3472 |
completed | April 10, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69d9803f6c508190bfadfbc2d00c2c64 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:03 p.m.