Triple
T37390281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arthur D. Healey |
E928685
|
entity |
| Predicate | hasNameInLaw |
P200637
|
FINISHED |
| Object | Walsh–Healey Public Contracts Act |
—
|
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: Walsh–Healey Public Contracts Act | Statement: [Arthur D. Healey, hasNameInLaw, Walsh–Healey Public Contracts Act]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameInLaw Context triple: [Arthur D. Healey, hasNameInLaw, Walsh–Healey Public Contracts Act]
-
A.
hasMarriedSurname
Indicates that a person’s current surname is the one they adopted through marriage.
-
B.
namedForSpouse
Indicates that one entity is named after the spouse of another entity.
-
C.
laterMarriedName
Indicates that the referenced name is a surname or full name a person adopted after a later marriage, replacing or succeeding their previous name.
-
D.
spouseNameAtMarriage
Indicates the full name a person’s spouse had at the time of their marriage.
-
E.
spouse name
Indicates that one entity is the legally recognized husband or wife of the other, specifying the partner’s name in a marital relationship.
- 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_69f76ebb10c481909b54b9dba263e29f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff9bed58dc8190a204816d4ed6c32c |
completed | May 9, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69ff9b69653c81908ab0d88055a66a88 |
completed | May 9, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69ff9bec9d748190869caebf6bf0c78f |
completed | May 9, 2026, 8:41 p.m. |
Created at: May 3, 2026, 4:16 p.m.