Triple
T23331696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hernando de Soto expedition |
E591460
|
entity |
| Predicate | sizeOfForce |
P49546
|
FINISHED |
| Object | approximately 600 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: approximately 600 men | Statement: [Hernando de Soto expedition, sizeOfForce, approximately 600 men]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sizeOfForce Context triple: [Hernando de Soto expedition, sizeOfForce, approximately 600 men]
-
A.
forceSize
chosen
Indicates a relationship where one entity specifies or constrains the magnitude or size of a force associated with another entity.
-
B.
commandingForceSize
Indicates the size or magnitude of the military or organizational force that is exercising command or control in a given context.
-
C.
isSmallForce
Indicates that the force involved has a relatively low magnitude compared to typical or relevant reference forces.
-
D.
sizeType
Indicates the kind or category of size associated with an entity, such as relative scale, measurement type, or size classification.
-
E.
hasForceStrength
Indicates that one entity possesses a certain level or degree of physical or exerted force strength in relation to another entity or context.
- 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_69e25d20156c81908c5c53195bd9c738 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f197edfbbc81908cb56507cd280737 |
completed | April 29, 2026, 5:32 a.m. |
| PD | Predicate disambiguation | batch_69effcf8ca2c8190887d4f4656617d21 |
completed | April 28, 2026, 12:19 a.m. |
Created at: April 17, 2026, 5:15 p.m.