Triple
T28926507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serdi |
E733662
|
entity |
| Predicate | regionStrategicFor |
P46323
|
FINISHED |
| Object | Roman Empire |
—
|
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: Roman Empire | Statement: [Serdi, regionStrategicFor, Roman Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionStrategicFor Context triple: [Serdi, regionStrategicFor, Roman Empire]
-
A.
strategicLocation
Indicates that an entity is positioned in a place of particular tactical or strategic importance relative to goals, resources, or other entities.
-
B.
strategicArea
chosen
Indicates that an entity is designated as an area of strategic importance or priority within a broader plan, operation, or context.
-
C.
regionOpposedExpansionIn
Indicates that a region actively resisted or opposed the expansion of another entity into its territory or sphere of influence.
-
D.
regionStrength
Indicates the relative level of influence, power, or dominance that one region holds within a specified context or comparison.
-
E.
regionFrom
Indicates that something originates from, is derived from, or is associated with a particular geographic or administrative region.
- 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_69f05b0b49b08190b8994b339c7980f6 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fd474b7e788190a9bb9b542d878f60 |
completed | May 8, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69fd46d8b2f0819099d92d72c902f60e |
completed | May 8, 2026, 2:13 a.m. |
Created at: April 28, 2026, 8:23 a.m.