Triple
T13857288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 18 U.S.C. §§ 2701–2712 |
E333098
|
entity |
| Predicate | hasShortName |
P1354
|
FINISHED |
| Object | SCA |
E333097
|
NE 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: SCA | Statement: [18 U.S.C. §§ 2701–2712, hasShortName, SCA]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SCA Context triple: [18 U.S.C. §§ 2701–2712, hasShortName, SCA]
-
A.
SCA
SCA is the National Rail station code for Scarborough railway station in North Yorkshire, England.
-
B.
SCA
chosen
SCA is a U.S. federal law that governs the privacy and disclosure of stored electronic communications and related data held by service providers.
-
C.
SCA
The SCA is South Africa’s highest court of appeal for non-constitutional matters, based in Bloemfontein.
-
D.
SCA
SCA is the commonly used abbreviation for Hay’at Qanāt as-Suways, the authority responsible for managing and operating Egypt’s Suez Canal.
-
E.
SCA
SCA is the common abbreviation for the Service Contract Act, a U.S. federal law that sets wage and benefit standards for employees working on government service contracts.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d81c5ba13c8190839315f54768acfd |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02dc9f488190b7181dcb7e304632 |
completed | April 14, 2026, 9:03 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7c70a59e8819090b750699993a107 |
completed | May 3, 2026, 10:07 p.m. |
Created at: April 9, 2026, 10:14 p.m.