Triple
T13029568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abstract Right |
E326396
|
entity |
| Predicate | treatsRightAs |
P107531
|
FINISHED |
| Object | right of the person as such |
—
|
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: right of the person as such | Statement: [Abstract Right, treatsRightAs, right of the person as such]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: treatsRightAs Context triple: [Abstract Right, treatsRightAs, right of the person as such]
-
A.
treatsCharacter
Indicates how one character behaves toward or interacts with another character, especially in terms of care, respect, or mistreatment.
-
B.
treatsLightAs
Indicates that an entity regards or handles light in a particular way or manner.
-
C.
treats
Indicates that one entity provides medical care or therapeutic intervention to another entity.
-
D.
protectsRight
Indicates that one entity safeguards, upholds, or defends the legal or moral rights of another entity.
-
E.
requiresEqualTreatmentWith
Indicates that one entity must be treated in the same way and to the same extent as another entity, without preferential or discriminatory differences.
- 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_69d8076cc45c81908123123f43e69266 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97efd18308190877b3269403b36e2 |
completed | April 10, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69d97dc39a0881908119c62e31bf6182 |
completed | April 10, 2026, 10:46 p.m. |
| PDg | Predicate description generation | batch_69d97e3df2288190a7f27d31d248bb7f |
completed | April 10, 2026, 10:48 p.m. |
Created at: April 9, 2026, 8:54 p.m.