Triple
T29104149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gothic forces |
E736716
|
entity |
| Predicate | sometimesServedAs |
P106622
|
FINISHED |
| Object | Roman foederati |
—
|
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 foederati | Statement: [Gothic forces, sometimesServedAs, Roman foederati]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sometimesServedAs Context triple: [Gothic forces, sometimesServedAs, Roman foederati]
-
A.
possiblyServedAs
chosen
Indicates that an entity may have held or fulfilled a particular role, position, or function, but this service is uncertain or not definitively confirmed.
-
B.
typicallyServedAs
Indicates that something is most commonly presented, used, or offered in a particular role, form, or function.
-
C.
alsoServesAs
Indicates that one entity has an additional role, function, or identity that it fulfills simultaneously with its primary one.
-
D.
alsoServedBy
Indicates that the same service, function, or role is additionally provided or fulfilled by another entity alongside the primary one.
-
E.
alsoServedAs
Indicates that an entity held an additional role or position beyond the primary one already mentioned.
- 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_69f077ec765c81909474c88bcc8bab43 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f661b842808190ac168c6f3d40d23c |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 11:14 a.m.