Triple
T36565345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baluarte de San Pedro |
E901960
|
entity |
| Predicate | partOfDefenseSystemAgainst |
P66390
|
FINISHED |
| Object | pirates |
—
|
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: pirates | Statement: [Baluarte de San Pedro, partOfDefenseSystemAgainst, pirates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfDefenseSystemAgainst Context triple: [Baluarte de San Pedro, partOfDefenseSystemAgainst, pirates]
-
A.
partOfDefenseLine
chosen
Indicates that one entity functions as a component or segment within the overall defensive formation or system of another entity.
-
B.
airDefenseSystem
Indicates a defensive military system designed to detect, track, and engage airborne threats such as aircraft or missiles.
-
C.
defensiveSystem
Indicates a system or mechanism whose primary function is to protect, guard, or defend an entity against threats or attacks.
-
D.
defenseSystems
Indicates the presence, use, or configuration of protective measures or mechanisms intended to defend an entity against threats or attacks.
-
E.
airDefenseSystemComponent
Indicates that one entity is a component or subsystem of an air defense system associated with another entity.
- 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_69f76e6416708190a9754b8c52d4e453 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a01185c46f0819089b4a2ad3c3e2f33 |
completed | May 10, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_6a0117e19e008190870663dd45084416 |
completed | May 10, 2026, 11:42 p.m. |
Created at: May 3, 2026, 4:11 p.m.