Triple
T5014690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regulation X |
E112710
|
entity |
| Predicate | significantlyAmendedEffective |
P28017
|
FINISHED |
| Object | January 2014 |
—
|
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: January 2014 | Statement: [Regulation X, significantlyAmendedEffective, January 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: significantlyAmendedEffective Context triple: [Regulation X, significantlyAmendedEffective, January 2014]
-
A.
amendedFor
Indicates that one entity has been modified or revised specifically to address, correct, or accommodate another entity.
-
B.
furtherAmendedBy
Indicates that an existing item (such as a document, law, or agreement) is modified again by a subsequent amendment, building on prior changes.
-
C.
amendedAt
chosen
Indicates the date and time at which an existing entity or record was modified or updated.
-
D.
isAmendmentTo
Indicates that one item formally modifies, revises, or adds to the content or terms of another item.
-
E.
partiallyAmendedBy
Indicates that an existing item (such as a document, law, or agreement) has been modified in part, but not completely replaced, by another item.
- 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_69bd4434acb8819086679dbeccc2fe54 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd732e0b848190858407920e7aefd0 |
completed | March 20, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69bd714cbc448190aa53a8a83d768b64 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:35 p.m.