Triple
T9899679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SOC 1 |
E182251
|
entity |
| Predicate | predecessorTerminology |
P97
|
FINISHED |
| Object | SAS 70 reports (conceptual predecessor) |
—
|
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: SAS 70 reports (conceptual predecessor) | Statement: [SOC 1, predecessorTerminology, SAS 70 reports (conceptual predecessor)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorTerminology Context triple: [SOC 1, predecessorTerminology, SAS 70 reports (conceptual predecessor)]
-
A.
predecessorInConcept
Indicates that one concept temporally or logically comes before another in a sequence or developmental progression.
-
B.
predecessor
chosen
Indicates that one entity comes before another in an ordered sequence or succession.
-
C.
predecessorName
Indicates that the value is the name of an entity that directly precedes another in an ordered sequence or lineage.
-
D.
predecessorNameUsage
Indicates that a name was used previously and has been replaced or superseded by a subsequent name in a sequence or lineage.
-
E.
predecessorGround
Indicates that one entity serves as the immediate prior version or state of another entity within a sequence or process.
- 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.