Triple
T28824505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Britannia Superior |
E727864
|
entity |
| Predicate | hasLegion |
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: [Britannia Superior, hasLegion, Legio II Augusta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLegion Context triple: [Britannia Superior, hasLegion, Legio II Augusta]
-
A.
hasColossiOf
Indicates that one entity possesses, contains, or is characterized by monumental statues or colossal figures associated with another entity.
-
B.
hasCultOrLegend
Indicates that an entity is associated with, or is the subject of, a cult, myth, or legendary tradition.
-
C.
hasRostrum
Indicates that one entity possesses or is characterized by a rostrum (a beak-like or snout-like projection).
-
D.
hasModernLegacyIn
Indicates that something continues to exert influence, relevance, or impact within a modern context, domain, or location.
-
E.
isLegendaryStatus
Indicates that an entity possesses a legendary status, typically signifying exceptional rarity, renown, or significance within a given context.
- 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_69f0319d09088190bbf14cdf1987792a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
| PDg | Predicate description generation | batch_69f75788d40c819083bf2567b3091585 |
completed | May 3, 2026, 2:11 p.m. |
Created at: April 28, 2026, 6:35 a.m.