Triple
T32311246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Negro Fort |
E825504
|
entity |
| Predicate | armamentSource |
P89764
|
FINISHED |
| Object | British military supplies |
—
|
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: British military supplies | Statement: [Negro Fort, armamentSource, British military supplies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: armamentSource Context triple: [Negro Fort, armamentSource, British military supplies]
-
A.
armamentOrigin
chosen
Indicates the source or place from which a weapon or armament originates or is supplied.
-
B.
armamentCategory
Indicates the classification of a weapon or military equipment according to its type or role in armament systems.
-
C.
armamentNote
Indicates a note or comment providing additional information or clarification about an armament or weapon-related detail.
-
D.
armamentIncludes
Indicates that a larger weapon system, vehicle, or platform has a specified weapon or piece of equipment as part of its armament.
-
E.
armamentCount
Indicates the number of weapons or armaments associated with an 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_69f3491213b88190a57094d8697a7455 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bdb74c708190833b4c7d332b1a0d |
completed | May 3, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:46 a.m.