Triple
T38024888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inspiration4 |
E948743
|
entity |
| Predicate | primaryDonor |
P44585
|
FINISHED |
| Object | Jared Isaacman |
E639419
|
NE 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: Jared Isaacman | Statement: [Inspiration4, primaryDonor, Jared Isaacman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryDonor Context triple: [Inspiration4, primaryDonor, Jared Isaacman]
-
A.
primaryPatron
chosen
Indicates that one entity serves as the main or chief supporter, sponsor, or benefactor of another entity.
-
B.
primaryRecipient
Indicates the entity that is the main or principal receiver of something, such as a message, resource, or benefit, in a given context.
-
C.
primaryParticipant
Indicates that an entity plays the main or most central role in a given event, activity, or relationship.
-
D.
primaryFor
Indicates that one entity serves as the main or principal option, resource, or association for another entity among possible alternatives.
-
E.
primaryHeir
Indicates that one entity is the main or principal inheritor of another entity’s estate, title, or rights.
- F. None of above.
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_69f76efd1bc48190a729097fe5177b61 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a4167fdf4bc81908f08567794749be8 |
completed | June 28, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:20 p.m.