Triple
T37346518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JOBS Act of 2012 |
E927189
|
entity |
| Predicate | titleVIName |
P201335
|
FINISHED |
| Object | Capital Expansion |
—
|
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: Capital Expansion | Statement: [JOBS Act of 2012, titleVIName, Capital Expansion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleVIName Context triple: [JOBS Act of 2012, titleVIName, Capital Expansion]
-
A.
titleVIProvides
Indicates that an entity provides or administers services, benefits, or programs that are subject to Title VI nondiscrimination requirements.
-
B.
titleIIIName
Indicates that one entity is the official Title III–specific name or designation associated with another entity.
-
C.
titleVariant
Indicates that one title is an alternative or variant form of another title referring to the same work or entity.
-
D.
titleOfTitle
Indicates that one title is the title of another title (e.g., a sub-title or alternate title associated with a primary title).
-
E.
titleKey
Indicates that one entity serves as a key or identifier used to reference or retrieve the title associated with another entity.
- F. None of above. chosen
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_69f76eb5e034819088e53ab5b7909a68 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffebbd9bac8190b3dca4b7252a2278 |
completed | May 10, 2026, 2:21 a.m. |
| PD | Predicate disambiguation | batch_69ffe93120a08190a44bb64d052eda78 |
completed | May 10, 2026, 2:10 a.m. |
| PDg | Predicate description generation | batch_69ffebbcef80819099714fa9b7fda762 |
completed | May 10, 2026, 2:21 a.m. |
Created at: May 3, 2026, 4:16 p.m.