Triple
T17948741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mr. Harris |
E448772
|
entity |
| Predicate | hasLegalRightClaimed |
P31301
|
FINISHED |
| Object | right to George Harris’s labor |
—
|
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 to George Harris’s labor | Statement: [Mr. Harris, hasLegalRightClaimed, right to George Harris’s labor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLegalRightClaimed Context triple: [Mr. Harris, hasLegalRightClaimed, right to George Harris’s labor]
-
A.
hasLegalRight
Indicates that an entity possesses an officially recognized legal entitlement or permission to perform an action or hold a claim regarding another entity.
-
B.
hasCollectiveRightClaim
Indicates that a group or collective entity asserts or holds a right or entitlement on behalf of its members.
-
C.
claimedRight
chosen
Indicates that an entity asserts or demands a right or entitlement in relation to another entity or resource.
-
D.
hasClaimOn
Indicates that one entity holds a right, entitlement, or demand over another entity or its resources.
-
E.
legalSystemClaimed
Indicates that a particular legal system asserts authority or jurisdiction over a given entity, situation, or matter.
- 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_69d8b9f8cca8819099836916c56b7c95 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4afaac780819097434b20b1f155d2 |
completed | April 19, 2026, 10:34 a.m. |
| PD | Predicate disambiguation | batch_69e3f8f2bd088190b1e22ad4d9cc8b13 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:21 a.m.