Triple
T731499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MacKenzie Scott |
E14839
|
entity |
| Predicate | dateSignedGivingPledge |
P439
|
FINISHED |
| Object | 2019 |
—
|
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: 2019 | Statement: [MacKenzie Scott, dateSignedGivingPledge, 2019]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateSignedGivingPledge Context triple: [MacKenzie Scott, dateSignedGivingPledge, 2019]
-
A.
dateSigned
chosen
Indicates the specific date on which an agreement, document, or contract was formally signed.
-
B.
announcedPledge
Indicates that an entity has publicly declared a commitment or promise, typically regarding future actions or contributions.
-
C.
signedFor
Indicates that one entity formally accepted or acknowledged receipt of something on behalf of another, typically by providing a signature.
-
D.
signedAs
Indicates that an entity has signed or endorsed something using a particular name, role, or identity.
-
E.
hasSignFor
Indicates that one entity displays, bears, or provides a sign, symbol, or notice that represents, directs attention to, or gives information about 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_69a4934d9930819099eed80096b0597d |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a66820548190b373deb117187c2c |
completed | March 1, 2026, 8:49 p.m. |
| PD | Predicate disambiguation | batch_69a4a4f9b7608190bf97c8418a26e632 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.