Triple
T5390408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virginia Constitution of 1776 |
E120307
|
entity |
| Predicate | rightsProtected |
P45186
|
FINISHED |
| Object | freedom of the press |
—
|
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: freedom of the press | Statement: [Virginia Constitution of 1776, rightsProtected, freedom of the press]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rightsProtected Context triple: [Virginia Constitution of 1776, rightsProtected, freedom of the press]
-
A.
rights
Indicates that an entity possesses entitlements, permissions, or legal/moral claims in relation to another entity or context.
-
B.
protectsRight
Indicates that one entity safeguards, upholds, or defends the legal or moral rights of another entity.
-
C.
rightsInclude
chosen
Indicates that one set of rights encompasses, contains, or subsumes another set of rights.
-
D.
rightsRecognizedIn
Indicates that certain rights are formally acknowledged or upheld within a specified context, such as a legal system, jurisdiction, or document.
-
E.
rightsSociety
Indicates that an entity holds legal, moral, or social rights in relation to a society or collective group.
- 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_69bd46354c648190a38b26f107010a96 |
completed | March 20, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69bd87185f788190bd5244a1f7dbb5c8 |
completed | March 20, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69bd8463a9c88190bd760378f3026180 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:04 p.m.