Triple
T30060567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moesia Prima |
E763866
|
entity |
| Predicate | sufferedInvasionsBy |
P21625
|
FINISHED |
| Object | Goths |
—
|
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: Goths | Statement: [Moesia Prima, sufferedInvasionsBy, Goths]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sufferedInvasionsBy Context triple: [Moesia Prima, sufferedInvasionsBy, Goths]
-
A.
invadedDuring
Indicates that one entity carried out an invasion of another entity within the temporal bounds of a specified event or period.
-
B.
wasInvadedBy
chosen
Indicates that a place or territory was subjected to an incursion or attack carried out by another entity or group.
-
C.
causedTerritorialLossesTo
Indicates that one entity was responsible for another entity losing control over some portion of its territory.
-
D.
conqueredInPartBy
Indicates that one entity has gained control over a portion, but not the entirety, of another entity through conquest.
-
E.
lastTerritoriesConqueredBy
Indicates that the referenced territories are the most recent ones taken control of through conquest by a specified 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_69f224716378819087a722e487832b70 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67ca34d4081909ea4b2b02523d46a |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 6:57 p.m.