Triple
T25714364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crocodilopolis |
E644819
|
entity |
| Predicate | cameUnderRuleOf |
P73014
|
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: [Crocodilopolis, cameUnderRuleOf, Roman Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cameUnderRuleOf Context triple: [Crocodilopolis, cameUnderRuleOf, Roman Empire]
-
A.
laterUnderRuleOf
Indicates that one entity came to be governed or ruled by another entity at a later point in time.
-
B.
concludedUnderRuler
Indicates that an event, agreement, or process was completed or finalized during the reign or authority of a specific ruler.
-
C.
historicallyUnderRuleOf
chosen
Indicates that one entity was historically governed, controlled, or ruled by another entity during a past period.
-
D.
formedUnderRuleOf
Indicates that one entity was created, established, or came into existence while another entity held governing authority or was in power.
-
E.
ruled in
Indicates that an authority, such as a court or judge, has made a formal decision or judgment in favor of a particular party or position.
- 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_69e77e8476fc8190bd5e9d05b89fad0a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fc610aac81909ee4722dcfcca67d |
completed | May 2, 2026, 1:30 p.m. |
| PD | Predicate disambiguation | batch_69f4938262ac8190b41f922d0407d272 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 21, 2026, 9:37 p.m.