Triple
T33077562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George Steptoe Washington |
E846407
|
entity |
| Predicate | managedEstateIn |
P188908
|
FINISHED |
| Object | Virginia |
—
|
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: Virginia | Statement: [George Steptoe Washington, managedEstateIn, Virginia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managedEstateIn Context triple: [George Steptoe Washington, managedEstateIn, Virginia]
-
A.
estateManaged
Indicates that one entity is responsible for administering, overseeing, or handling the affairs and assets of another entity’s estate.
-
B.
hasEstateManager
Indicates that an entity is responsible for managing, overseeing, or administering the estate or property of another entity.
-
C.
managesPropertyFor
Indicates that one entity is responsible for overseeing, operating, or administering a property on behalf of another entity.
-
D.
estateManagementActivity
Indicates activities involved in administering, maintaining, or overseeing an estate or property and its associated affairs.
-
E.
improvedEstate
Indicates that an estate has undergone enhancements, developments, or upgrades that increase its value or utility.
- 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_69f3495405b88190967af2157b43b896 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fbaf18085481908c774e8f8bbb9a41 |
completed | May 6, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69fbaebbb7f88190b4edfd9b83550aad |
completed | May 6, 2026, 9:12 p.m. |
Created at: May 1, 2026, 1:25 a.m.