Triple
T34373151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pachomian Rule |
E882216
|
entity |
| Predicate | originEmpire |
P158090
|
FINISHED |
| Object | Roman Empire |
E1239
|
NE 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: Roman Empire | Statement: [Pachomian Rule, originEmpire, Roman Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originEmpire Context triple: [Pachomian Rule, originEmpire, Roman Empire]
-
A.
originatingEmpire
chosen
Indicates the empire from which an entity, such as a person, object, or event, originally comes or was first established.
-
B.
governingEmpire
Indicates that one entity serves as the ruling imperial power that controls or governs another entity.
-
C.
provinceOfEmpire
Indicates that a given province belongs to, is governed by, or forms an administrative part of a particular empire.
-
D.
typeOfEmpire
Indicates the specific kind or classification of empire that an entity belongs to or represents.
-
E.
foundedInEmpire
Indicates that an entity (such as an organization, city, or institution) was established during the existence or rule of a specified empire.
- F. None of above.
Provenance (4 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_69f349bf5d7481908dd5da4cbdf74047 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37049cabfc8190817a649de7ddf46d |
completed | June 20, 2026, 9:22 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:59 a.m.