Triple
T8088852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rheinbund |
E188802
|
entity |
| Predicate | requiredToProvide |
P80428
|
FINISHED |
| Object | troops for Napoleon’s campaigns |
—
|
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: troops for Napoleon’s campaigns | Statement: [Rheinbund, requiredToProvide, troops for Napoleon’s campaigns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiredToProvide Context triple: [Rheinbund, requiredToProvide, troops for Napoleon’s campaigns]
-
A.
requiredBy
Indicates that one entity depends on or cannot function properly without another entity being present, completed, or satisfied.
-
B.
requiredInformation
Indicates that certain data or details are necessary and must be provided for a process, action, or relationship to proceed or be valid.
-
C.
requires
Indicates that one entity must exist, occur, or be satisfied before another entity can exist, occur, or be carried out.
-
D.
complianceRequiredFor
Indicates that one entity must adhere to or satisfy the rules, standards, or conditions defined by another entity.
-
E.
evaluationRequirement
Indicates that one entity imposes or specifies conditions under which another entity must be assessed, tested, or evaluated.
- F. None of above. chosen
Provenance (4 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_69ca82b7b3e88190b9041ab0ef28b3cb |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb421c717c819089dd88c30a6401aa |
completed | March 31, 2026, 3:40 a.m. |
| PD | Predicate disambiguation | batch_69cb04a14cd88190a79ed26cbeec1c33 |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14be17208190bb51c3dfcb613f20 |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:29 p.m.