Triple
T24890040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke of Lennox |
E622969
|
entity |
| Predicate | laterGoverningLaw |
P158743
|
FINISHED |
| Object | British peerage law |
—
|
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: British peerage law | Statement: [Duke of Lennox, laterGoverningLaw, British peerage law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterGoverningLaw Context triple: [Duke of Lennox, laterGoverningLaw, British peerage law]
-
A.
laterLegalJurisdiction
Indicates that one legal jurisdiction succeeds or replaces another jurisdiction at a later point in time.
-
B.
governingLawTraditionally
Indicates that a particular law or legal system has historically and customarily been applied to govern a given relationship, contract, or situation.
-
C.
governsBodyOfLaw
Indicates that one entity has authoritative control over the creation, interpretation, or enforcement of a particular body of law.
-
D.
legalProtectionJurisdiction
Indicates the jurisdiction or legal authority under which an entity is granted legal protection.
-
E.
legalLicenseJurisdiction
Indicates the legal authority or geographic area under whose laws a particular license is granted, valid, or enforced.
- 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_69e2fac597708190a922bf39a49ec70a |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f48b9b687881908fd87a2f5fa0b1e7 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f48060597c8190a4414e4e4fcb1fec |
completed | May 1, 2026, 10:28 a.m. |
| PDg | Predicate description generation | batch_69f48b9058d081908ec9af261ee092e2 |
completed | May 1, 2026, 11:16 a.m. |
Created at: April 18, 2026, 5:26 a.m.