Triple
T1143797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Batavi |
E23515
|
entity |
| Predicate | suppliedUnitsTo |
P17063
|
FINISHED |
| Object | Roman auxiliary cohorts across the empire |
—
|
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: Roman auxiliary cohorts across the empire | Statement: [Batavi, suppliedUnitsTo, Roman auxiliary cohorts across the empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: suppliedUnitsTo Context triple: [Batavi, suppliedUnitsTo, Roman auxiliary cohorts across the empire]
-
A.
suppliesTo
chosen
Indicates that one entity provides or delivers goods, services, or resources to another entity.
-
B.
numberOfUnits
Indicates the quantity or count of discrete units associated with an entity or relationship.
-
C.
unitOfMeasure
Indicates that one entity specifies the standard unit in which the quantity or value of another entity is measured.
-
D.
associatedWithUnit
Indicates that one entity has a connection, linkage, or affiliation with a particular unit (such as a division, department, or organizational subunit).
-
E.
componentUnit
Indicates that one entity functions as a constituent or sub-unit that forms part of a larger composite 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_69a493ef399c8190b04b9146d2314f59 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bc5008d8819095c1ffb5db5b4911 |
completed | March 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69a4bb4d4104819084027a043c6118cb |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:44 p.m.