Triple
T12775226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pierce Inverarity |
E305350
|
entity |
| Predicate | roleInWill |
P268
|
FINISHED |
| Object | testator |
—
|
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: testator | Statement: [Pierce Inverarity, roleInWill, testator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInWill Context triple: [Pierce Inverarity, roleInWill, testator]
-
A.
willBequest
Indicates a relationship where a person specifies in a will that certain assets or rights are to be given to another party after their death.
-
B.
makesWill
Indicates that an entity creates or executes a legal will for another entity or for themselves.
-
C.
will
Indicates that an entity is going to perform an action or be in a certain state in the future.
-
D.
followsWillOf
Indicates that one entity acts in accordance with, or submits its decisions and behavior to, the intentions, desires, or directives of another entity.
-
E.
role
chosen
Indicates the function, position, or responsibility that one entity holds in relation to another within a given context.
- 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_69d7bdf2b43c819098ae5aa68e61ea58 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96df6b3c88190b0bbe70de8ddcbf3 |
completed | April 10, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69d9640ba0688190973e4e7ec8d4a8e0 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:29 p.m.