Triple
T18799246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Noisseville |
E459720
|
entity |
| Predicate | GermanForcesStrength |
P31239
|
FINISHED |
| Object | approximately 90000 |
—
|
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: approximately 90000 | Statement: [Battle of Noisseville, GermanForcesStrength, approximately 90000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: GermanForcesStrength Context triple: [Battle of Noisseville, GermanForcesStrength, approximately 90000]
-
A.
GermanicForces
Indicates a relationship where certain forces or military units are identified as belonging to or associated with Germanic groups.
-
B.
PrussianStrength
Indicates a relationship where an entity possesses or exhibits the military, political, or institutional power characteristic of Prussia.
-
C.
PrussianStrengthApprox
chosen
Indicates an approximate assessment or estimation of the strength or power associated with Prussia in a given context.
-
D.
germanUnit
Indicates that an entity is a military or organizational unit that belongs to, originates from, or is associated with Germany.
-
E.
GermanLoss
Indicates that Germany experiences a loss, defeat, or negative outcome in the specified context or event.
- 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_69d8d398c7d4819091cb2f7e48948aeb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5a02273b481909bc250144a0ace32 |
completed | April 20, 2026, 3:40 a.m. |
| PD | Predicate disambiguation | batch_69e48d16dd34819096e096d0c0e4c15c |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:53 a.m.