Triple
T11920404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Walsh Act |
E283636
|
entity |
| Predicate | commissionSize |
P102365
|
FINISHED |
| Object | three to five commissioners |
—
|
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: three to five commissioners | Statement: [Walsh Act, commissionSize, three to five commissioners]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commissionSize Context triple: [Walsh Act, commissionSize, three to five commissioners]
-
A.
commissionType
Indicates the specific kind or category of commission arrangement that applies to a given transaction or relationship.
-
B.
commissionName
Indicates the name or official title assigned to a particular commission.
-
C.
commissionStatus
Indicates the current state or phase of a commission-related process, such as whether it is pending, active, completed, or cancelled.
-
D.
commissionCreated
Indicates that a new commission has been initiated or established as a result of some creating action or event.
-
E.
commissionContext
Indicates the circumstances, conditions, or situational details under which a commission (such as a task, order, or assignment) is created, carried out, or applies between entities.
- 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_69d6ab2c07e88190ba13b0d21fd6cf33 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8e8dff77481908cacf6ad03df34ac |
completed | April 10, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69d8bb3632ac8190b13e53c2b5db7125 |
completed | April 10, 2026, 8:56 a.m. |
| PDg | Predicate description generation | batch_69d8dd0ba0f88190b7d5e358c27ca184 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 8, 2026, 9:45 p.m.