Triple
T3448257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bengal European Regiment |
E72727
|
entity |
| Predicate | hasSoldierType |
P6154
|
FINISHED |
| Object | European officers |
—
|
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: European officers | Statement: [Bengal European Regiment, hasSoldierType, European officers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSoldierType Context triple: [Bengal European Regiment, hasSoldierType, European officers]
-
A.
isRegularArmyUnit
Indicates that the entity functions as a formal, organized military unit within a country's regular (non-irregular) armed forces.
-
B.
hasWeaponType
Indicates that an entity is associated with or equipped with a specific type or category of weapon.
-
C.
typeOfTroops
chosen
Indicates the specific category or kind of military forces involved in or associated with an entity or event.
-
D.
soldierCaste
Indicates that an entity belongs to, or is characterized as part of, a soldier or warrior class within a social or organizational hierarchy.
-
E.
hasCavalrySetting
Indicates that an entity is associated with a context, configuration, or environment specifically involving cavalry.
- 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_69ad85b05c848190b7a28ceec2bd7b74 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adba705d988190b76d905751a337ee |
completed | March 8, 2026, 6:05 p.m. |
| PD | Predicate disambiguation | batch_69adae0255b48190a9069f7871c7a012 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:16 p.m.