Triple
T9433359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Labourd |
E227438
|
entity |
| Predicate | historicalLegalSystem |
P17298
|
FINISHED |
| Object | Basque customary 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: Basque customary law | Statement: [Labourd, historicalLegalSystem, Basque customary law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalLegalSystem Context triple: [Labourd, historicalLegalSystem, Basque customary law]
-
A.
historicalLaw
Indicates that the referenced law or legal provision existed and was in effect during a past historical period, rather than being current.
-
B.
historicalJurisdiction
Indicates that one entity previously held legal or administrative authority over another entity during a past time period.
-
C.
legalHistory
Indicates that there exists a record of past legal actions, cases, or statuses associated with an entity.
-
D.
hasLawTradition
chosen
Indicates that one legal system, jurisdiction, or entity follows or is based on a particular legal tradition or family of law.
-
E.
coexistingLegalTradition
Indicates that multiple legal traditions or systems exist and operate simultaneously within the same social or institutional 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_69ca8437a7ac81908651de48f2d2141d |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd7e61a114819081fc4a2ad39c96ba |
completed | April 1, 2026, 8:21 p.m. |
| PD | Predicate disambiguation | batch_69cca55548488190b171ae695a3212de |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:49 p.m.