Triple
T6029232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sir Joseph Mason |
E134257
|
entity |
| Predicate | makesWill |
P68849
|
FINISHED |
| Object | will concerning Orley Farm |
—
|
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: will concerning Orley Farm | Statement: [Sir Joseph Mason, makesWill, will concerning Orley Farm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: makesWill Context triple: [Sir Joseph Mason, makesWill, will concerning Orley Farm]
-
A.
will
Indicates that an entity is going to perform an action or be in a certain state in the future.
-
B.
followsWillOf
Indicates that one entity acts in accordance with, or submits its decisions and behavior to, the intentions, desires, or directives of another entity.
-
C.
signedBeforeDeathOf
Indicates that one entity signed something at a time earlier than the death of another specified entity.
-
D.
willSignedOn
Indicates that a person has formally signed a will on a specific date or occasion, thereby validating or executing that testamentary document.
-
E.
canMake
Indicates that one entity has the ability or capacity to create, produce, or assemble another entity.
- 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_69c0087515148190a97475d412563865 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c0560fdc84819093abba13054ea1ee |
completed | March 22, 2026, 8:50 p.m. |
| PD | Predicate disambiguation | batch_69c049e9a68c81909da0cfe4779ce9b5 |
completed | March 22, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69c04e8c5bfc8190b986a7071d1b23e3 |
completed | March 22, 2026, 8:18 p.m. |
Created at: March 22, 2026, 4:07 p.m.