Triple
T7847305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HITECH Act |
E181954
|
entity |
| Predicate | titleInARRA |
P38
|
FINISHED |
| Object | Title XIII of Division A |
—
|
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: Title XIII of Division A | Statement: [HITECH Act, titleInARRA, Title XIII of Division A]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleInARRA Context triple: [HITECH Act, titleInARRA, Title XIII of Division A]
-
A.
titles
Indicates that one entity holds a formal title, designation, or name associated with another entity.
-
B.
title
chosen
Indicates that one entity serves as the formal name or designation of another entity.
-
C.
titleRepresents
Indicates that a given title stands for, denotes, or symbolizes a particular concept, role, work, or entity.
-
D.
titleStart
Indicates that one entity’s title begins with the text or substring represented by the other entity.
-
E.
involvesTitle
Indicates that the relationship or action includes or makes reference to a specific title (such as a role, honorific, or formal designation).
- 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_69ca8285d6488190a95d4c02d7354b53 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb164105fc8190a60aaa27dd619d5a |
completed | March 31, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69cae92180f88190ae3d44c3de7adc93 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:49 p.m.