Triple
T1842126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waldeck |
E41198
|
entity |
| Predicate | typeOfTroopContract |
P405
|
FINISHED |
| Object | auxiliary service contracts |
—
|
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: auxiliary service contracts | Statement: [Waldeck, typeOfTroopContract, auxiliary service contracts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfTroopContract Context triple: [Waldeck, typeOfTroopContract, auxiliary service contracts]
-
A.
typeOfTroops
Indicates the specific category or kind of military forces involved in or associated with an entity or event.
-
B.
typeOfContract
chosen
Indicates the specific kind or category of contractual agreement that applies between the related entities.
-
C.
suppliedTroopsTo
Indicates that one entity provided military personnel or forces to another entity.
-
D.
contractUnit
Indicates that one entity serves as a contractual unit or party within a contract relationship involving another entity.
-
E.
isRegularArmyUnit
Indicates that the entity functions as a formal, organized military unit within a country's regular (non-irregular) armed forces.
- 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_69a88648cd44819093303206d96d76ad |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb32d35508190bf1c487dffbecaf0 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafdb0d2c8190a67f584e67979fa3 |
completed | March 7, 2026, 4:55 a.m. |
Created at: March 4, 2026, 7:33 p.m.