Triple
T28772959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | gens Sergia |
E726459
|
entity |
| Predicate | associatedEventThroughMember |
P141717
|
FINISHED |
| Object | Catilinarian Conspiracy |
E726460
|
NE 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: Catilinarian Conspiracy | Statement: [gens Sergia, associatedEventThroughMember, Catilinarian Conspiracy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedEventThroughMember Context triple: [gens Sergia, associatedEventThroughMember, Catilinarian Conspiracy]
-
A.
associatedEventType
Indicates that one entity is linked to another by the type or category of event with which it is associated.
-
B.
associatedThrough
chosen
Indicates that two entities are connected or related to each other by means of a specified intermediary, context, or linkage.
-
C.
associatedMeeting
Indicates a relationship where one entity is linked or connected to a particular meeting, typically as the meeting that is relevant or related to it.
-
D.
associatedWithCorporateEvent
Indicates that an entity has a connection or involvement with a specific corporate event.
-
E.
associatedWithEventHost
Indicates that an entity has a relationship or connection with the host of a particular event.
- F. None of above.
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_69f03199997c8190b6ae43fb19312443 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_6a01ca0db6f08190bed479584114e63d |
completed | May 11, 2026, 12:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a24a268ad048190ae49f8cac538831e |
completed | June 6, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_6a01c96ff4a08190a4fbf0cebbda95b4 |
completed | May 11, 2026, 12:20 p.m. |
Created at: April 28, 2026, 6:16 a.m.