Triple
T18544296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | aedile |
E453181
|
entity |
| Predicate | couldHold |
P132097
|
FINISHED |
| Object | judicial powers in minor cases |
—
|
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: judicial powers in minor cases | Statement: [aedile, couldHold, judicial powers in minor cases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: couldHold Context triple: [aedile, couldHold, judicial powers in minor cases]
-
A.
canHold
Indicates that one entity has the capacity or ability to contain, support, or carry another entity.
-
B.
canBeHeld
Indicates that an entity is capable of being physically grasped, supported, or carried by another entity.
-
C.
canBeHeldWith
Indicates that two entities are compatible or suitable to be held or used together at the same time.
-
D.
canBeHeldIn
Indicates that one entity is capable of being contained, hosted, or conducted within another entity.
-
E.
cannotBeHeldBy
Indicates that one entity is not allowed or not able to possess, carry, or be in control of another entity.
- 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_69d8d388b0c881908e610a1c45b52640 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e534b935c48190a34b17eeae4fd583 |
completed | April 19, 2026, 8:02 p.m. |
| PD | Predicate disambiguation | batch_69e469e274a48190a570b25cfef4d890 |
completed | April 19, 2026, 5:36 a.m. |
| PDg | Predicate description generation | batch_69e46d2b93bc8190a6070018d7046547 |
completed | April 19, 2026, 5:50 a.m. |
Created at: April 10, 2026, 11:38 a.m.