Triple
T12037218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Appius Claudius Crassus |
E286571
|
entity |
| Predicate | belongsToDynastyOrFamily |
P91745
|
FINISHED |
| Object | Claudii |
—
|
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: Claudii | Statement: [Appius Claudius Crassus, belongsToDynastyOrFamily, Claudii]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToDynastyOrFamily Context triple: [Appius Claudius Crassus, belongsToDynastyOrFamily, Claudii]
-
A.
associatedWithDynasty
Indicates that an entity has a historical, political, cultural, or familial connection to a specific dynasty.
-
B.
refersToPersonWithDynasty
Indicates that one entity makes reference to a person specifically identified or characterized by their association with a particular dynasty.
-
C.
belongsToFamily
Indicates that an entity is a member of, or is associated as part of, a specific family group.
-
D.
dynasticallyLinkedTo
Indicates a relationship where two entities are connected through a line of succession, inheritance, or familial rule within or across dynasties.
-
E.
partOfDynasty
chosen
Indicates that an entity belongs to, or is a constituent member of, a particular dynasty.
- 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_69d6ab4669e48190b59246358b0383ab |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9100b4ca8819084845ca4c13e34ce |
completed | April 10, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69d902bac9e08190aa1a99c835f29542 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:47 p.m.