Triple
T9513219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mina Miller Edison |
E229453
|
entity |
| Predicate | estateRole |
P88483
|
FINISHED |
| Object | manager of the Glenmont estate |
—
|
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: manager of the Glenmont estate | Statement: [Mina Miller Edison, estateRole, manager of the Glenmont estate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: estateRole Context triple: [Mina Miller Edison, estateRole, manager of the Glenmont estate]
-
A.
estate
Indicates a legal or ownership relationship in which a person or entity holds rights, interests, or control over property or assets.
-
B.
ownerOccupation
Indicates that the occupation or job role of an entity that owns something is being specified or described.
-
C.
property
Indicates that one entity possesses, is characterized by, or has an attribute or quality associated with another entity.
-
D.
ownsOrLeases
Indicates that one entity has legal rights to use or control another entity either through ownership or through a lease agreement.
-
E.
estateVariantName
Indicates that one name is an alternative or variant designation used for the same estate.
- 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_69ca84777560819084cddd999badc1aa |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd986aa99c8190b2eaa7f9b111aa2e |
completed | April 1, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cca567ca448190bf4bcce8ce7dd54f |
completed | April 1, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69cca89d0f0c8190b4528990fe708fca |
completed | April 1, 2026, 5:09 a.m. |
Created at: March 30, 2026, 7:58 p.m.