Triple
T233821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polish 1st Independent Parachute Brigade |
E4464
|
entity |
| Predicate | eliteUnit |
P1198
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Polish 1st Independent Parachute Brigade, eliteUnit, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eliteUnit Context triple: [Polish 1st Independent Parachute Brigade, eliteUnit, true]
-
A.
typeOfTroops
Indicates the specific category or kind of military forces involved in or associated with an entity or event.
-
B.
hasSpecialUnit
chosen
Indicates that an entity possesses or is associated with a distinct, designated unit that has a special role, function, or status.
-
C.
militaryOrganization
Indicates that an entity functions as, or is associated with, a structured armed forces or defense-related organization.
-
D.
involvedUnit
Indicates that a particular unit (such as a group, organization, or division) participates in, is associated with, or plays a role in the referenced event or activity.
-
E.
paramilitaryWing
Indicates that one entity functions as the paramilitary or armed wing associated with another entity, typically an organization or movement.
- 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_69a257363ffc81909757bde7ab3404da |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25f14f72081908182e76300b59358 |
completed | Feb. 28, 2026, 3:20 a.m. |
| PD | Predicate disambiguation | batch_69a25b5c8c888190b5544e687736b373 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.