Triple
T7048120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Territorial Force |
E163693
|
entity |
| Predicate | sizeAtOutbreakOfWWI |
P74734
|
FINISHED |
| Object | over 250000 personnel |
—
|
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: over 250000 personnel | Statement: [Territorial Force, sizeAtOutbreakOfWWI, over 250000 personnel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sizeAtOutbreakOfWWI Context triple: [Territorial Force, sizeAtOutbreakOfWWI, over 250000 personnel]
-
A.
preWorldWarIIPopulationEstimate
Indicates an estimated value for an entity’s population during the period before the start of World War II.
-
B.
positionOnWorldWarI
Indicates a person’s or group’s stance, opinion, or policy regarding World War I.
-
C.
percentageDestroyedInWWIIApproximate
Indicates the approximate proportion of something that was destroyed during World War II.
-
D.
numberOfWorldWarIUnknowns
Indicates the quantity of unknown or unspecified entities associated with World War I.
-
E.
statusDuringWorldWarII
Indicates the role, condition, or classification an entity had specifically during the period of World War II.
- 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_69c6885f598c8190b6b6495c59d8d962 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e4a3c36c819080942c59f1830ae8 |
completed | March 27, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69c6e1bb602081908bfa6186a1f5a4b4 |
completed | March 27, 2026, 7:59 p.m. |
| PDg | Predicate description generation | batch_69c6e4a15b088190bee9a23e94aaac53 |
completed | March 27, 2026, 8:12 p.m. |
Created at: March 27, 2026, 2:37 p.m.