Triple
T27708681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Internal Revenue Code Section 402(g) |
E698618
|
entity |
| Predicate | wasAddedBy |
P90748
|
FINISHED |
| Object | Revenue Act of 1978 |
—
|
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: Revenue Act of 1978 | Statement: [Internal Revenue Code Section 402(g), wasAddedBy, Revenue Act of 1978]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasAddedBy Context triple: [Internal Revenue Code Section 402(g), wasAddedBy, Revenue Act of 1978]
-
A.
addedTo
Indicates that one entity has been included or incorporated into another entity, typically as a new component, member, or element.
-
B.
addedFor
Indicates that one entity was created, included, or introduced specifically for the benefit, use, or purpose of another entity.
-
C.
introducedByUser
Indicates that something was brought into existence, initiated, or added as a result of an action performed by a specific user.
-
D.
insertedBy
chosen
Indicates that one entity was placed, added, or introduced into another entity or context by a specific agent or process.
-
E.
amendedBy
Indicates that one entity has been modified, revised, or updated as a result of changes made by another 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_69ef590f655c81909f93893b3b3219b2 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f635c9422c8190bc1ba40260b41fbc |
completed | May 2, 2026, 5:35 p.m. |
| PD | Predicate disambiguation | batch_69f62c1a92648190835a2c5250d8c758 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 3:01 p.m.