Triple
T1703406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman aediles |
E36815
|
entity |
| Predicate | couldHoldImperium |
P32437
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Roman aediles, couldHoldImperium, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: couldHoldImperium Context triple: [Roman aediles, couldHoldImperium, no]
-
A.
coEmperorWith
Indicates that two individuals simultaneously share the position and authority of emperor within the same imperial system.
-
B.
canHold
Indicates that one entity has the capacity or ability to contain, support, or carry another entity.
-
C.
boundEmperorBy
Indicates that one entity has constrained, restricted, or subjugated an emperor through some form of binding control or obligation.
-
D.
heldThat
Indicates that an entity (often a person or authority) maintained, asserted, or concluded that a particular proposition or judgment is true.
-
E.
hasEmperor
Indicates that an entity is ruled or governed by an emperor.
- F. None of above. chosen
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_69a88617439c819094ffb5d16a0f6307 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69ab75ad24408190814069e6e3ef9e59 |
completed | March 7, 2026, 12:47 a.m. |
| PD | Predicate disambiguation | batch_69aa61bad17c8190861b92cfb423f68f |
completed | March 6, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69ab75ac1408819086b22b3cd0672a79 |
completed | March 7, 2026, 12:47 a.m. |
Created at: March 4, 2026, 7:30 p.m.