Triple
T25482293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Byzantine period |
E638606
|
entity |
| Predicate | hasMilitarySystem |
P15789
|
FINISHED |
| Object | theme system |
—
|
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: theme system | Statement: [Byzantine period, hasMilitarySystem, theme system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMilitarySystem Context triple: [Byzantine period, hasMilitarySystem, theme system]
-
A.
militarySystem
chosen
Indicates a relationship where an entity functions as, belongs to, or is characterized by a particular military organizational or operational system.
-
B.
usesMilitarySystemSimilarTo
Indicates that one entity employs a military system that is comparable in structure, doctrine, or operational methods to that of another entity.
-
C.
hasMilitaryType
Indicates that an entity is associated with or classified under a specific military category, role, or type.
-
D.
hasMissileDetectionSystem
Indicates that an entity is equipped with a system capable of detecting missiles.
-
E.
hasNATOCompatibleSystems
Indicates that an entity possesses systems or equipment that are compatible with NATO standards and can interoperate with NATO forces.
- 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_69e75dbabeac8190bab30628f8b799d4 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b37a5648190b10d33ae205ccfee |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 21, 2026, 2:31 p.m.