Triple
T9569247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Byzantine Empire (as ally during 1453 siege) |
E230871
|
entity |
| Predicate | internalIssue |
P33633
|
FINISHED |
| Object | religious division over union with Rome |
—
|
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: religious division over union with Rome | Statement: [Byzantine Empire (as ally during 1453 siege), internalIssue, religious division over union with Rome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: internalIssue Context triple: [Byzantine Empire (as ally during 1453 siege), internalIssue, religious division over union with Rome]
-
A.
hasInternalIssue
chosen
Indicates that an entity is experiencing a problem, fault, or malfunction originating within itself or its internal components or processes.
-
B.
issueType
Indicates the specific category or classification assigned to an issue within a tracking or management context.
-
C.
knownIssue
Indicates that the subject has an issue or problem that is already identified, recognized, or documented.
-
D.
internalOutcome
Indicates an outcome or result that arises from within an entity, system, or process itself, rather than from external factors.
-
E.
underlyingIssue
Indicates that one situation, problem, or condition is the fundamental cause or root problem behind another.
- 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_69ca847f22188190a56e4a97625bef22 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd998940c881909f9025512cf72fe9 |
completed | April 1, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69ccd59b960c8190966a8870a2426bd5 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:04 p.m.