Triple
T8073026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scardina v. Masterpiece Cakeshop |
E188420
|
entity |
| Predicate | partyRoleOfAutumnScardina |
P80346
|
FINISHED |
| Object | attorney |
—
|
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: attorney | Statement: [Scardina v. Masterpiece Cakeshop, partyRoleOfAutumnScardina, attorney]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partyRoleOfAutumnScardina Context triple: [Scardina v. Masterpiece Cakeshop, partyRoleOfAutumnScardina, attorney]
-
A.
roleInSeason
Indicates the specific role or function an entity has within a particular season of a series or competition.
-
B.
playsInRole
Indicates that an entity performs or appears in a specific role within a production, event, or context.
-
C.
intraPartyRole
Indicates a role or function that an entity holds within a specific political party or internal party structure.
-
D.
sonRole
Indicates that one entity holds the role or relationship of a son with respect to another entity.
-
E.
associatedPlayerRole
Indicates a relationship where a specific role or function is linked to, or held by, a particular player.
- 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_69ca82b50c708190863f661d438e68df |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb40482200819086c639f64c01fbb5 |
completed | March 31, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69cb049f1614819087360d1a4c6f0faa |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14be17208190bb51c3dfcb613f20 |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:27 p.m.