Triple
T33087268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porcii Laecae |
E846673
|
entity |
| Predicate | typicalOfficeHeld |
P45587
|
FINISHED |
| Object | senator |
—
|
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: senator | Statement: [Porcii Laecae, typicalOfficeHeld, senator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalOfficeHeld Context triple: [Porcii Laecae, typicalOfficeHeld, senator]
-
A.
aboutOfficeHeld
Indicates that one entity is related to, or provides information about, a specific office or position that is or was held by another entity.
-
B.
officeHeldOf
chosen
Indicates that a specific office or position is (or was) held by a particular person or entity.
-
C.
officeHeldDuring
Indicates that a person occupied a specific official position during a particular time period.
-
D.
typeOfOffice
Indicates the specific category or kind of office that an office entity belongs to (e.g., executive, legislative, judicial, or other office types).
-
E.
possibleOfficeHeld
Indicates that an entity may have held, or is a candidate to have held, a particular office or position, without asserting it as a confirmed fact.
- 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_69f34954d46c8190a04a159cc5f99efd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:26 a.m.