Triple
T9899677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SOC 1 |
E182251
|
entity |
| Predicate | reportDistribution |
P20605
|
FINISHED |
| Object | restricted-use report |
—
|
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: restricted-use report | Statement: [SOC 1, reportDistribution, restricted-use report]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reportDistribution Context triple: [SOC 1, reportDistribution, restricted-use report]
-
A.
reportPublisher
Indicates that one entity is the organization or individual responsible for publishing a given report.
-
B.
reportsWithin
Indicates that one entity submits or delivers a report to another entity within a specified time frame or boundary.
-
C.
reportType
chosen
Indicates the specific category or kind of report associated with an entity or action.
-
D.
reportsSegment
Indicates that one entity provides or delivers a report specifically about a particular segment or subsection of data, content, or activity.
-
E.
report
Indicates that one entity formally provides information or an account about another entity, event, or situation, typically for documentation, communication, or evaluation purposes.
- 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_69ca82876f8081909cf75df0f99bb13f |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cdb4adc03481909e0f657db01e5bab |
completed | April 2, 2026, 12:13 a.m. |
| PD | Predicate disambiguation | batch_69cd1d872d50819096b7ab166a8decf1 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:40 p.m.