Triple
T23939497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fortress of Humaitá |
E602740
|
entity |
| Predicate | hasArtillery |
P19273
|
FINISHED |
| Object | heavy guns |
—
|
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: heavy guns | Statement: [Fortress of Humaitá, hasArtillery, heavy guns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArtillery Context triple: [Fortress of Humaitá, hasArtillery, heavy guns]
-
A.
hasArtilleryUse
Indicates that one entity employs, operates, or makes use of artillery in relation to another entity or context.
-
B.
hasArtilleryCaliber
Indicates that an artillery piece is characterized by or equipped with a specific caliber (diameter) of its gun barrel or ammunition.
-
C.
hasArtilleryCorps
Indicates that an entity possesses, includes, or is associated with an artillery corps as part of its military forces.
-
D.
artilleryUsedBy
Indicates that a particular artillery asset is operated or employed by a specified user, such as a military unit, organization, or country.
-
E.
artilleryType
chosen
Indicates the specific category or kind of artillery associated with an entity or event.
- 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_69e2953cf6e081909b8e25a10a52dddc |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1cfa40398819095e24521f3bf8622 |
completed | April 29, 2026, 9:30 a.m. |
| PD | Predicate disambiguation | batch_69f1615518088190a206f54e2fdb14a3 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:08 p.m.