Triple
T125523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black Reports |
E2539
|
entity |
| Predicate | legalAuthorityLevel |
P4976
|
FINISHED |
| Object | secondary source |
—
|
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: secondary source | Statement: [Black Reports, legalAuthorityLevel, secondary source]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalAuthorityLevel Context triple: [Black Reports, legalAuthorityLevel, secondary source]
-
A.
legalBasis
Indicates the legal rule, authority, or justification under which an action, decision, or status is established or carried out.
-
B.
legalRecognition
Indicates that an authority formally acknowledges the validity, status, or rights associated with an entity, relationship, or action under the law.
-
C.
legalStandardHistoricallyAssociatedWith
Indicates that a particular legal standard has been historically linked or traditionally associated with another legal concept, practice, or context.
-
D.
hasLegalStatus
Indicates that an entity possesses a particular legal classification, recognition, or standing under law.
-
E.
legalSubject
Indicates that an entity is the bearer of legal rights, duties, or responsibilities within a legal relationship or context.
- 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_69a251b54ea88190b18281669f59b4c0 |
completed | Feb. 28, 2026, 2:23 a.m. |
| NER | Named-entity recognition | batch_69a2573e4e6481908252dfef2e34f46e |
completed | Feb. 28, 2026, 2:47 a.m. |
| PD | Predicate disambiguation | batch_69a2564a54948190ba30bee858173b27 |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a256ea776081908fec36c3fdfb8d84 |
completed | Feb. 28, 2026, 2:46 a.m. |
Created at: Feb. 28, 2026, 2:27 a.m.