Triple
T8311919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tribunes of the Plebs |
E194609
|
entity |
| Predicate | couldNotBe |
P73536
|
FINISHED |
| Object | patrician |
—
|
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: patrician | Statement: [Tribunes of the Plebs, couldNotBe, patrician]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: couldNotBe Context triple: [Tribunes of the Plebs, couldNotBe, patrician]
-
A.
cannot
Indicates that one entity lacks the ability, permission, or possibility to perform an action or participate in a specified relationship with another entity.
-
B.
couldPass
Indicates that one entity had the ability or potential to move through, overcome, or be accepted by another entity or barrier.
-
C.
canBe
Indicates that one entity has the potential, permission, or capability to become, perform as, or be classified as another entity.
-
D.
cannotExpress
Indicates that one entity is unable to convey, articulate, or communicate something (such as a feeling, idea, or message) to another entity.
-
E.
notToBe
chosen
Indicates that one entity is explicitly specified as not being identical to, equivalent to, or in the state of another entity or condition.
- 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_69ca82e6e2648190a31eaf6f4f757b2a |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7f504ca8819087fb1f731f7a7cfd |
completed | March 31, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69cb70bb3a708190bc705222092da614 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:54 p.m.