Triple
T24369693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Third Army of the North German Confederation |
E614296
|
entity |
| Predicate | includedContingent |
P1393
|
FINISHED |
| Object | Bavarian troops |
—
|
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: Bavarian troops | Statement: [Third Army of the North German Confederation, includedContingent, Bavarian troops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedContingent Context triple: [Third Army of the North German Confederation, includedContingent, Bavarian troops]
-
A.
includes
chosen
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
-
B.
contingentOn
Indicates that the occurrence, validity, or outcome of one event or condition depends on the fulfillment or existence of another.
-
C.
includedWith
Indicates that one entity is provided or packaged together as part of another entity.
-
D.
containedWith
Indicates that one entity is located or kept inside the bounds or interior space of another entity.
-
E.
sometimesIncluded
Indicates that one entity is occasionally, but not always, contained within, part of, or present in association with 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_69e2d7e1e010819098b95eb3f905943d |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2938a4f188190932af66f57be0756 |
completed | April 29, 2026, 11:26 p.m. |
| PD | Predicate disambiguation | batch_69f287bb1b2c81909c2e7fcc392ad143 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:01 a.m.