Triple
T18210684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robert Todd Lincoln Beckwith |
E436022
|
entity |
| Predicate | managedProperty |
P51437
|
FINISHED |
| Object | family farm in Virginia |
—
|
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: family farm in Virginia | Statement: [Robert Todd Lincoln Beckwith, managedProperty, family farm in Virginia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managedProperty Context triple: [Robert Todd Lincoln Beckwith, managedProperty, family farm in Virginia]
-
A.
metaProperty
Indicates that one property functions as a higher-level descriptor or attribute about another property, rather than about an entity directly.
-
B.
managedIn
Indicates that one entity is administered, operated, or overseen within the scope, control, or jurisdiction of another entity.
-
C.
typeOfPropertyManaged
chosen
Indicates the specific category or kind of property that an entity is responsible for managing.
-
D.
ownedProperty
Indicates that one entity possesses legal ownership or control over another entity as property.
-
E.
managedAs
Indicates that one entity is administered, controlled, or handled in the same way or under the same policies, procedures, or classification as 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_69d8b90dba6481908e119eb9aa4ca0cb |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4e228a7fc81909cfcf11cf7ce1360 |
completed | April 19, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_69e4332155d88190b106d0dceb4554af |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:32 a.m.