Triple
T15911911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Legio XV Apollinaris |
E385868
|
entity |
| Predicate | standardStrength |
P2981
|
FINISHED |
| Object | approximately 5000 legionaries |
—
|
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 5000 legionaries | Statement: [Legio XV Apollinaris, standardStrength, approximately 5000 legionaries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardStrength Context triple: [Legio XV Apollinaris, standardStrength, approximately 5000 legionaries]
-
A.
secondaryStrength
Indicates a secondary or supporting level of strength or influence that complements a primary one in the relationship between entities.
-
B.
initialStrength
Indicates the original or starting level of strength associated with an entity before any changes or influences occur.
-
C.
estimatedStrength
chosen
Indicates that a value represents an approximate or inferred level, magnitude, or intensity of something rather than a precisely measured strength.
-
D.
standardPar
Indicates that two entities are parallel and conform to a recognized or defined standard of parallelism.
-
E.
standardWithin
Indicates that one entity conforms to, or falls within the limits of, a specified standard defined by another entity.
- 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_69d86da686e4819097cbf3b1fc2d881d |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e172b48b308190bc430b2308cbc75b |
completed | April 16, 2026, 11:37 p.m. |
| PD | Predicate disambiguation | batch_69e142cf5c548190a931f7b58144cd31 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:52 a.m.