Triple
T34390146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaius Pius Esuvius Tetricus |
E882672
|
entity |
| Predicate | wasRecognizedBy |
P45463
|
FINISHED |
| Object | Gallic legions |
—
|
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: Gallic legions | Statement: [Gaius Pius Esuvius Tetricus, wasRecognizedBy, Gallic legions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasRecognizedBy Context triple: [Gaius Pius Esuvius Tetricus, wasRecognizedBy, Gallic legions]
-
A.
wasRecognizedIn
Indicates that an entity received acknowledgment, credit, or an award within a specified context, event, or time frame.
-
B.
wasRecognizedAs
Indicates that an entity was formally identified, acknowledged, or designated as having a particular role, status, or quality.
-
C.
hasNotableRecognitionFor
Indicates that an entity has received notable recognition, such as awards, honors, or distinctions, specifically for another entity or achievement.
-
D.
reconocidaPor
chosen
Indicates that an entity is recognized, acknowledged, or honored by another entity.
-
E.
areRecognizedBy
Indicates that one entity acknowledges, identifies, or accepts another entity as valid, known, or legitimate.
- 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_69f349c0219881909393bbbc1edc8161 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71fb1ab3881908e2f7c0e6f23db49 |
completed | May 3, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f71cc6397881909aaad37a9daa8a7e |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 1:59 a.m.