Triple
T25966248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heed Their Rising Voices |
E645677
|
entity |
| Predicate | relatedLegalArea |
P2167
|
FINISHED |
| Object | defamation law |
—
|
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: defamation law | Statement: [Heed Their Rising Voices, relatedLegalArea, defamation law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedLegalArea Context triple: [Heed Their Rising Voices, relatedLegalArea, defamation law]
-
A.
relatedLegalSystem
Indicates that there is an association or connection between two legal systems, such as influence, similarity, shared origin, or mutual relevance.
-
B.
relatedLegalConcept
Indicates that one legal concept is connected or associated with another through a relevant legal relationship or context.
-
C.
notableAreaOfLaw
Indicates that a person or entity is particularly recognized or distinguished in a specific field or area of law.
-
D.
legalMatters
Indicates that one entity is involved with, concerned about, or responsible for legal issues, processes, or obligations related to another entity or context.
-
E.
legalArea
chosen
Indicates the specific field or branch of law that a legal matter, case, or document pertains to.
- 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_69e77e85efc08190997da7fcf98bd300 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69fd8ccbd4c88190b13aae0673b3c821 |
completed | May 8, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69fd8ae2227c819089546f5c3629799e |
completed | May 8, 2026, 7:04 a.m. |
Created at: April 22, 2026, 8:48 a.m.