Triple
T2497793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lordship of Biscay |
E52391
|
entity |
| Predicate | hasLaw |
P26796
|
FINISHED |
| Object | Biscayan charter |
—
|
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: Biscayan charter | Statement: [Lordship of Biscay, hasLaw, Biscayan charter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLaw Context triple: [Lordship of Biscay, hasLaw, Biscayan charter]
-
A.
legalAct
Indicates that an entity performs, enacts, or is involved in a formal legal action, measure, or proceeding under a legal framework.
-
B.
containsLawOn
Indicates that one entity (such as a document, code, or regulation) includes or sets forth legal provisions concerning another entity or subject.
-
C.
hasLegalEffect
Indicates that an action, document, or condition produces recognized legal consequences or enforceable rights and obligations.
-
D.
hasLegalIssue
Indicates that an entity is involved in, associated with, or subject to a legal problem, dispute, or proceeding.
-
E.
hasLegalForceIn
chosen
Indicates that something (such as a law, regulation, or agreement) is legally valid, binding, and enforceable within a specified jurisdiction or context.
- 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_69ab4957b3a88190adf968ae0c1b931c |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd1ad2f8c81908853e97d75081e84 |
completed | March 7, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69abd0bba5348190bb4637d3165cb339 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:46 p.m.