Triple
T5009906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kerykes |
E112591
|
entity |
| Predicate | hereditaryStatus |
P60296
|
FINISHED |
| Object | offices transmitted within the family |
—
|
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: offices transmitted within the family | Statement: [Kerykes, hereditaryStatus, offices transmitted within the family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hereditaryStatus Context triple: [Kerykes, hereditaryStatus, offices transmitted within the family]
-
A.
hereditaryInFamily
chosen
Indicates that a trait, condition, or characteristic is passed down through generations within the same family.
-
B.
inheritanceStatus
Indicates the type or condition of inheritance rights or succession status that applies between related parties.
-
C.
hasHereditaryChief
Indicates that an entity is led or governed by a chief whose position is inherited through family lineage.
-
D.
geneticStatus
Indicates the genetic condition or variant state an entity has in relation to a specific gene or set of genes.
-
E.
ancestralStatus
Indicates that one entity holds a particular ancestral or lineage-based relationship or status in relation to another entity.
- 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_69bd4434acb8819086679dbeccc2fe54 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd730bdb208190bebd7f22839ab6e5 |
completed | March 20, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69bd714cbc448190aa53a8a83d768b64 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:35 p.m.