Triple
T30450725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guthrie family |
E774704
|
entity |
| Predicate | hasArchiveManagedBy |
P24644
|
FINISHED |
| Object | Nora Guthrie |
—
|
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: Nora Guthrie | Statement: [Guthrie family, hasArchiveManagedBy, Nora Guthrie]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArchiveManagedBy Context triple: [Guthrie family, hasArchiveManagedBy, Nora Guthrie]
-
A.
hasArchiveArea
Indicates that an entity includes or is associated with a designated area used for archiving or long-term storage of materials.
-
B.
isOftenManagedBy
Indicates that an entity is frequently or typically overseen, directed, or administered by another entity.
-
C.
isManagedThrough
Indicates that one entity is administered, controlled, or operated by means of another entity, typically specifying the mechanism, channel, or system used for its management.
-
D.
isManagedFor
Indicates that one entity is administered, overseen, or controlled on behalf of another entity or purpose.
-
E.
hasManagement
chosen
Indicates that one entity exercises managerial authority or oversight over 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_69f22493ef9c8190ae8c2afcb7f994c8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
Created at: April 29, 2026, 8:09 p.m.