Triple
T15002236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Byzantine Empire under Isaurian dynasty |
E374117
|
entity |
| Predicate | hasSupportGroup |
P3508
|
FINISHED |
| Object | iconoclasts |
—
|
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: iconoclasts | Statement: [Byzantine Empire under Isaurian dynasty, hasSupportGroup, iconoclasts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSupportGroup Context triple: [Byzantine Empire under Isaurian dynasty, hasSupportGroup, iconoclasts]
-
A.
hasSupporterGroup
chosen
Indicates that an entity is associated with a group of supporters that backs, promotes, or advocates for it.
-
B.
supportsGroupType
Indicates that one entity is compatible with or able to support a particular category or type of group.
-
C.
hasUserGroup
Indicates that a user is associated with, belongs to, or is a member of a specific user group.
-
D.
hasSiteGroup
Indicates that an entity is associated with or belongs to a particular site group.
-
E.
hasSupportCategory
Indicates that an entity is associated with a particular type or category of support it receives or provides.
- 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_69d85ccc84388190aa151e5173370c8d |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded7312ae48190bdaf91ecced6657e |
completed | April 15, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69de9a6531a88190acde65199a477350 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:54 a.m.