Triple
T35817389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke's Laws |
E1035399
|
entity |
| Predicate | locationOfFirstPromulgation |
P2108
|
FINISHED |
| Object | Hempstead, Long Island |
E235740
|
NE 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: Hempstead, Long Island | Statement: [Duke's Laws, locationOfFirstPromulgation, Hempstead, Long Island]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfFirstPromulgation Context triple: [Duke's Laws, locationOfFirstPromulgation, Hempstead, Long Island]
-
A.
firstPromulgatedUnder
Indicates the authority, regime, or leadership under which something (typically a law, policy, or decree) was initially formally issued or enacted.
-
B.
yearOfPromulgation
Indicates the specific year in which something, typically a law or formal decree, was officially enacted or put into effect.
-
C.
dateOfPromulgation
Indicates the date on which a law, decree, or official act is formally proclaimed and put into effect.
-
D.
placeOfEnactment
chosen
Indicates the location where an event, action, or legal act is formally carried out or put into effect.
-
E.
promulgatedAt
Indicates the time or date at which an official rule, law, or document is formally issued or put into effect.
- F. None of above.
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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3891792bf0819098f892061f2249ab |
completed | June 22, 2026, 1:35 a.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:06 p.m.