Triple
T31092183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frank McLaury |
E792418
|
entity |
| Predicate | legalStatusInTombstone |
P197200
|
FINISHED |
| Object | suspected cattle rustler |
—
|
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: suspected cattle rustler | Statement: [Frank McLaury, legalStatusInTombstone, suspected cattle rustler]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalStatusInTombstone Context triple: [Frank McLaury, legalStatusInTombstone, suspected cattle rustler]
-
A.
burialStatus
Indicates the state or condition of whether and how an entity has been buried.
-
B.
hasBurialRestriction
Indicates that there is a rule, condition, or limitation governing how, where, or whether a burial may take place.
-
C.
hasTombDesignation
Indicates that an entity has been assigned a specific formal designation or identifier for its tomb.
-
D.
hasGravestone
Indicates that one entity possesses, is associated with, or is commemorated by a gravestone.
-
E.
isCemeteryFor
Indicates that one entity serves as the burial ground designated for another entity, such as a community, group, or location.
- F. None of above. chosen
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_69f224cf157c81909e2d2bd88c9282c3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe7bfc94bc81909eeec946e8c1c450 |
completed | May 9, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69fe7b74a1188190886f128e07f712da |
completed | May 9, 2026, 12:10 a.m. |
| PDg | Predicate description generation | batch_69fe7bfb71b08190bed5c33e4ab7afff |
completed | May 9, 2026, 12:12 a.m. |
Created at: April 29, 2026, 9:02 p.m.