Triple
T28655696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosemary Woodhouse |
E725323
|
entity |
| Predicate | trustsInitially |
P32325
|
FINISHED |
| Object | Guy Woodhouse |
—
|
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: Guy Woodhouse | Statement: [Rosemary Woodhouse, trustsInitially, Guy Woodhouse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trustsInitially Context triple: [Rosemary Woodhouse, trustsInitially, Guy Woodhouse]
-
A.
trusts
chosen
Indicates that one entity has confidence in the reliability, integrity, or intentions of another entity.
-
B.
trusteeshipSystem
Indicates a relationship in which one entity holds and manages authority or responsibility over another entity or territory on its behalf, typically under an established oversight or governance framework.
-
C.
heldInTrustFor
Indicates that one party holds an asset, right, or interest on behalf of and for the benefit of another party, subject to fiduciary or trust obligations.
-
D.
typeOfTrust
Indicates the specific kind or category of trust that characterizes the relationship between entities.
-
E.
entrustedTo
Indicates that responsibility, care, or control of something has been formally given by one party to another.
- 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_69f01d84f5f0819087ab5e6143b14ed7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651ac855481908e30c3b345d31356 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 4:55 a.m.