Triple
T7290245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italian Cohort |
E163972
|
entity |
| Predicate | likelySize |
P6061
|
FINISHED |
| Object | approximately 480–600 soldiers |
—
|
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 480–600 soldiers | Statement: [Italian Cohort, likelySize, approximately 480–600 soldiers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: likelySize Context triple: [Italian Cohort, likelySize, approximately 480–600 soldiers]
-
A.
approximateSize
chosen
Indicates that one entity has a size that is roughly or approximately equal to the size of another entity.
-
B.
sizeStatus
Indicates the relative size condition or classification of one entity in relation to another or to a defined standard.
-
C.
includesSizeRange
Indicates that one entity specifies or covers a particular range of sizes associated with another entity.
-
D.
sizeDescription
Indicates a relationship where one entity provides descriptive information about the size or scale of another entity.
-
E.
hasDimensionsApprox
Indicates that an entity has physical dimensions that are known only approximately, rather than as exact measurements.
- 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_69c6886093b88190a254b1ce6db8bae7 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6eb6d4e308190af6b8c237988d7d8 |
completed | March 27, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69c6e76c5fbc8190b378830082f11cb0 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3 p.m.