Triple
T37346517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JOBS Act of 2012 |
E927189
|
entity |
| Predicate | titleVName |
P38
|
FINISHED |
| Object | Private Company Flexibility and Growth |
—
|
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: Private Company Flexibility and Growth | Statement: [JOBS Act of 2012, titleVName, Private Company Flexibility and Growth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleVName Context triple: [JOBS Act of 2012, titleVName, Private Company Flexibility and Growth]
-
A.
titleVariant
Indicates that one title is an alternative or variant form of another title referring to the same work or entity.
-
B.
titleOfTitle
Indicates that one title is the title of another title (e.g., a sub-title or alternate title associated with a primary title).
-
C.
title
chosen
Indicates that one entity serves as the formal name or designation of another entity.
-
D.
titleThrough
Indicates a relationship where one entity holds or is identified by a specific title by means of, or via the mediation of, another entity or context.
-
E.
titleSubjectName
Indicates that the predicate specifies the name of the subject associated with a given title.
- 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_69f76eb5e034819088e53ab5b7909a68 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffe8ebe9fc8190b1934a3c4074370c |
completed | May 10, 2026, 2:09 a.m. |
| PD | Predicate disambiguation | batch_69ffe83a5de88190bed3e8bac86e8760 |
completed | May 10, 2026, 2:06 a.m. |
Created at: May 3, 2026, 4:16 p.m.