Triple
T11826038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Specific Relief Act 1877 |
E281261
|
entity |
| Predicate | doesNotPrimarilyProvide |
P101700
|
FINISHED |
| Object | damages |
—
|
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: damages | Statement: [Specific Relief Act 1877, doesNotPrimarilyProvide, damages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doesNotPrimarilyProvide Context triple: [Specific Relief Act 1877, doesNotPrimarilyProvide, damages]
-
A.
doesNotPrimarilyContain
Indicates that one entity does not have another entity as its main or predominant component, element, or content.
-
B.
doesNotServe
Indicates that one entity explicitly does not provide a service, function, or role to another entity.
-
C.
doesNotPrimarilyHonor
Indicates that the subject does not chiefly or mainly give recognition, tribute, or commemoration to the object.
-
D.
doesNotAutomaticallyProvide
Indicates that something is not supplied or made available by default and requires an explicit action or request to be provided.
-
E.
notPrimarilyIntendedFor
Indicates that something is used or occurs in a way that is not its main or original purpose or target.
- 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_69d6ab276f8c8190b1966a0ef11349ac |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a5eb299481909de3c0e85628fbe4 |
completed | April 10, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69d8a251fc08819095933f1d13c3b742 |
completed | April 10, 2026, 7:10 a.m. |
| PDg | Predicate description generation | batch_69d8a43cc0c881909fed7cd759fe90b1 |
completed | April 10, 2026, 7:18 a.m. |
Created at: April 8, 2026, 9:43 p.m.