Triple
T35448091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isca Dumnoniorum |
E1024541
|
entity |
| Predicate | legion |
P180866
|
FINISHED |
| Object | Legio II Augusta |
—
|
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: Legio II Augusta | Statement: [Isca Dumnoniorum, legion, Legio II Augusta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legion Context triple: [Isca Dumnoniorum, legion, Legio II Augusta]
-
A.
legionNumber
Indicates the numerical designation assigned to a specific legion within a larger military or organizational structure.
-
B.
hasLegion
chosen
Indicates that an entity possesses, commands, or is associated with a specific legion or group of legions.
-
C.
legionStationed
Indicates that a specific legion is stationed or deployed at a particular location.
-
D.
legendarium
Indicates a relationship where a work, element, or concept belongs to, is part of, or is defined within a particular fictional legendarium or mythic narrative universe.
-
E.
Hauptquartier
Indicates that one entity serves as the main headquarters or central administrative base for 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_69f76df8089481909f0018266ee881b7 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.