Triple
T34083749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marries former escort Willa Ferreyra |
E874119
|
entity |
| Predicate | hasGroomPartnerBeforeMarriage |
P100538
|
FINISHED |
| Object | Willa Ferreyra |
—
|
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: Willa Ferreyra | Statement: [Marries former escort Willa Ferreyra, hasGroomPartnerBeforeMarriage, Willa Ferreyra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGroomPartnerBeforeMarriage Context triple: [Marries former escort Willa Ferreyra, hasGroomPartnerBeforeMarriage, Willa Ferreyra]
-
A.
marriageBefore
Indicates that one marriage event occurred earlier in time than another marriage event.
-
B.
partnerBeforeMarriage
chosen
Indicates that one entity was the romantic or life partner of another entity prior to their marriage.
-
C.
marriedBefore
Indicates that one entity entered into a marriage at an earlier time than the other entity.
-
D.
partnerInMarriageDuring
Indicates that two entities are spouses of each other during a specified time period.
-
E.
hasMarriage
Indicates a marital relationship exists between the two entities, specifying that they are or were legally married to each other.
- 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_69f349a61d448190b74642f325d3eb7a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
Created at: May 1, 2026, 1:52 a.m.