Triple
T30162780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tungri |
E766712
|
entity |
| Predicate | raisedUnit |
P169362
|
FINISHED |
| Object | Cohors I Tungrorum |
—
|
NE NERFINISHED |
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: Cohors I Tungrorum | Statement: [Tungri, raisedUnit, Cohors I Tungrorum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raisedUnit Context triple: [Tungri, raisedUnit, Cohors I Tungrorum]
-
A.
raisedTo
Indicates that one entity has been elevated, lifted, or brought up to a higher level, position, or state by another entity.
-
B.
raisedUnder
Indicates that one entity was brought up, nurtured, or reared under the care, authority, or influence of another entity.
-
C.
raisedDuring
Indicates that one entity was brought up, nurtured, or developed within the time period or circumstances defined by another entity.
-
D.
raisedOn
Indicates that an entity was nurtured, brought up, or spent its formative period in a particular place, environment, or context.
-
E.
raisedFrom
Indicates that one entity has been elevated, derived, or brought up from another prior state, source, or condition.
- F. None of above. chosen
Provenance (4 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_69f2247a968881909d79c18f2bfcb275 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67f0488bc819089fbd2d2478158d3 |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f67d31cc60819084f64bd056e1ea4d |
completed | May 2, 2026, 10:39 p.m. |
Created at: April 29, 2026, 7:22 p.m.