Triple
T6174171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buna |
E137776
|
entity |
| Predicate | hasGuardForce |
P31894
|
FINISHED |
| Object | SS guards |
—
|
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: SS guards | Statement: [Buna, hasGuardForce, SS guards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGuardForce Context triple: [Buna, hasGuardForce, SS guards]
-
A.
hasReserveForces
Indicates that an entity possesses additional military or security personnel kept in reserve for potential future deployment or use.
-
B.
hasSecurityTeam
chosen
Indicates that an entity is supported or protected by a designated security team responsible for its safety or security operations.
-
C.
garrisonedForce
Indicates that a military force is stationed in and occupies a specific location, typically for defense or control.
-
D.
hasForceInterventionBrigade
Indicates that an entity includes or is supported by a designated force intervention brigade as part of its operational structure or mission.
-
E.
defenseForces
Indicates a relationship where one entity serves as the military or protective force responsible for defending 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_69c008a68c508190a8d78245c865960e |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05d94c47481909745b2533926a1ca |
completed | March 22, 2026, 9:22 p.m. |
| PD | Predicate disambiguation | batch_69c055f7f12881908e21c04e9b752ba4 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:18 p.m.