Triple
T1428114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dignitatis Humanae |
E30380
|
entity |
| Predicate | groundsRightIn |
P9529
|
FINISHED |
| Object | dignity of the human person |
—
|
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: dignity of the human person | Statement: [Dignitatis Humanae, groundsRightIn, dignity of the human person]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: groundsRightIn Context triple: [Dignitatis Humanae, groundsRightIn, dignity of the human person]
-
A.
ownerOfRightOfWay
Indicates that one entity holds the legal right to pass through or use a specific path, route, or area on another entity’s property.
-
B.
listsGrounds
chosen
Indicates that one entity enumerates or specifies the reasons, bases, or justifications (grounds) associated with another entity.
-
C.
hasGrounds
Indicates that one entity possesses or includes a physical area of land or outdoor space associated with it.
-
D.
establishesRight
Indicates that one entity creates or confers a legal or formal entitlement or privilege upon another entity.
-
E.
ground
Indicates that one entity is in contact with or supported by the ground or a ground-like surface.
- 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_69a498fb823c8190a67ce4c4837e641a |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c500a9888190a16fbb1ec97a79c9 |
completed | March 1, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69a4c4771c9481908ae47c959debbe77 |
completed | March 1, 2026, 10:57 p.m. |
Created at: March 1, 2026, 8 p.m.