Triple
T13285730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | gens Domitia |
E316438
|
entity |
| Predicate | statusInRepublic |
P41805
|
FINISHED |
| Object | plebeian but influential |
—
|
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: plebeian but influential | Statement: [gens Domitia, statusInRepublic, plebeian but influential]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInRepublic Context triple: [gens Domitia, statusInRepublic, plebeian but influential]
-
A.
governmentStatus
Indicates the type or condition of governance or political authority that an entity currently holds or is subject to.
-
B.
constitutionStatus
Indicates the legal or formal status of an entity as defined or recognized by a constitution.
-
C.
politicalStatusContext
chosen
Indicates the situational or contextual conditions under which a particular political status holds or is evaluated.
-
D.
statusInRepublicOfIreland
Indicates the legal or official status that an entity holds within the jurisdiction of the Republic of Ireland.
-
E.
statusInRussia
Indicates the legal, social, or operational condition or standing that something or someone has specifically within the context of Russia.
- 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_69d806b349908190a9a61dd9323bf153 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6535688190a5a4549b7be2d611 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:27 p.m.