Triple
T32003960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman collegium |
E817210
|
entity |
| Predicate | canSueOrBeSued |
P173106
|
FINISHED |
| Object | in Roman courts |
—
|
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: in Roman courts | Statement: [Roman collegium, canSueOrBeSued, in Roman courts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canSueOrBeSued Context triple: [Roman collegium, canSueOrBeSued, in Roman courts]
-
A.
canBeSuedAs
Indicates that one entity has legal standing or capacity to be the target of a lawsuit initiated by another entity.
-
B.
canBeSuedFor
Indicates that one party is legally liable or potentially subject to legal action by another party for a specified cause or wrongdoing.
-
C.
mayBeSuedUnder
Indicates that one entity is legally subject to being sued or brought to court under a specified law, statute, or legal framework by another entity.
-
D.
legalSubject
Indicates that an entity is the bearer of legal rights, duties, or responsibilities within a legal relationship or context.
-
E.
legalCodeFocus
Indicates that something is specifically concerned with, centered on, or primarily addressing a particular legal code or body of law.
- 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_69f348f8ce388190ae84376b1f348f12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b3fef2308190840009a605f422f3 |
completed | May 3, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69f6b21da77081908c5c015c4606d344 |
completed | May 3, 2026, 2:25 a.m. |
Created at: May 1, 2026, 12:14 a.m.