Triple
T33563547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warehouse Act of 1916 |
E859692
|
entity |
| Predicate | enactedInTheYear |
P24044
|
FINISHED |
| Object | 1916 |
—
|
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: 1916 | Statement: [Warehouse Act of 1916, enactedInTheYear, 1916]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enactedInTheYear Context triple: [Warehouse Act of 1916, enactedInTheYear, 1916]
-
A.
enactedDuring
Indicates that an action, event, or state occurred within the temporal span of a specified time period or event.
-
B.
yearOfPromulgation
chosen
Indicates the specific year in which something, typically a law or formal decree, was officially enacted or put into effect.
-
C.
yearEnteredIntoForce
Indicates the year in which an agreement, law, treaty, or similar instrument officially became legally effective or operational.
-
D.
enactedWith
Indicates that an action, law, or policy was formally established or brought into effect through the involvement or authority of a specified agent or instrument.
-
E.
legislatedOn
Indicates that a legislative body has formally considered, debated, or enacted laws or regulations concerning a particular subject or entity.
- 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_69f3497c1d288190a844ea699914e038 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f714fe7c819095c70dcf4164ed24 |
completed | May 3, 2026, 7:19 a.m. |
| PD | Predicate disambiguation | batch_69f6f6632dfc8190af85e258c8519207 |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:40 a.m.