Triple
T29572164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silvian dynasty |
E753341
|
entity |
| Predicate | hasMemberCognomen |
P109315
|
FINISHED |
| Object | Silvius |
—
|
NE NERFINISHED |
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: Silvius | Statement: [Silvian dynasty, hasMemberCognomen, Silvius]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMemberCognomen Context triple: [Silvian dynasty, hasMemberCognomen, Silvius]
-
A.
memberHasCognomen
chosen
Indicates that a member is associated with or bears a specific cognomen (surname or additional family name).
-
B.
hasMemberBySurname
Indicates that a group or collection includes a member identified by a specific surname.
-
C.
hasComponentSurname
Indicates that an entity’s full name includes a specified surname as one of its component parts.
-
D.
hasCharacterWithSurname
Indicates that an entity (such as a work or story) includes at least one character whose surname matches the specified name.
-
E.
memberHasPraenomen
Indicates that a member is associated with or bears a specific praenomen (personal given name).
- 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_69f0ef7fcb4881908a933110adb9bda1 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69fd553d7cb881908d243e7a9f30ac85 |
completed | May 8, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fd514dcb1c81908333c70d7edd79c9 |
completed | May 8, 2026, 2:58 a.m. |
Created at: April 28, 2026, 5:59 p.m.