Triple
T27423656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laurie Schaub |
E690416
|
entity |
| Predicate | partnerInActivityWith |
P82864
|
FINISHED |
| Object | Matt Schaub |
—
|
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: Matt Schaub | Statement: [Laurie Schaub, partnerInActivityWith, Matt Schaub]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partnerInActivityWith Context triple: [Laurie Schaub, partnerInActivityWith, Matt Schaub]
-
A.
partnerInActWith
chosen
Indicates that two or more entities jointly participate as partners in carrying out the same act or action.
-
B.
partnerInOrganizationWith
Indicates that two entities are associated as partners within the same organization or organizational context.
-
C.
partnerInWorkOf
Indicates a collaborative relationship where one entity works together with another on a shared task, project, or professional activity.
-
D.
partnerInActivismWith
Indicates that two entities collaborate or are closely associated with each other in activism or social/political advocacy efforts.
-
E.
invitesParticipationOf
Indicates that one entity actively requests or encourages another entity to take part in an activity, event, or process.
- 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_69ef52003fb48190b0f1295246182a86 |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f661b58ac48190907b6c6e9ccc2c59 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 27, 2026, 12:40 p.m.