Triple
T5187424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spanish Blue Division |
E117066
|
entity |
| Predicate | totalPersonnelServed |
P24266
|
FINISHED |
| Object | over 45000 men |
—
|
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 45000 men | Statement: [Spanish Blue Division, totalPersonnelServed, over 45000 men]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: totalPersonnelServed Context triple: [Spanish Blue Division, totalPersonnelServed, over 45000 men]
-
A.
crewServed
Indicates that the operation or use of something requires a coordinated effort by multiple people acting together as a crew.
-
B.
estimatedNumberOfPeopleSaved
Indicates the approximate count of individuals whose lives were preserved or harm was averted as a result of a particular action, intervention, or entity.
-
C.
personnelStrength
chosen
Indicates the number or capacity of people assigned to or available for a particular unit, organization, or operation.
-
D.
numberOfFloorsServed
Indicates the total count of distinct floors that are served or accessed by a given entity (such as an elevator or service system).
-
E.
servedUntil
Indicates the ending time or date up to which an entity held a position, role, or service.
- 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_69bd44620ff48190bcac01782107a397 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd79c3e9e08190848be4208b72f310 |
completed | March 20, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69bd77b7e8b4819092ec3965e11f2dea |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:46 p.m.