Triple
T29426156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Araba |
E746298
|
entity |
| Predicate | hasHistoricalCharter |
P8747
|
FINISHED |
| Object | fueros of Álava |
—
|
NE NERFINISHED |
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: fueros of Álava | Statement: [Araba, hasHistoricalCharter, fueros of Álava]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricalCharter Context triple: [Araba, hasHistoricalCharter, fueros of Álava]
-
A.
hasCharter
chosen
Indicates that an entity possesses, is governed by, or operates under a formal charter or foundational document.
-
B.
hasRoyalCharter
Indicates that an entity has been formally granted a royal charter by a monarch or royal authority.
-
C.
hasTownCharterFromYear
Indicates that an entity possesses an official town charter that has been in effect since the specified year.
-
D.
hasCharterStatus
Indicates that an entity possesses a specific charter designation or status granted by an authoritative body.
-
E.
introducedLegalCharter
Indicates that an entity formally established or brought into effect a legal charter governing another entity or domain.
- 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_69f0a7a06e0081908add494075912eb4 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69fd49f6dbac81909744373a357b7982 |
completed | May 8, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69fd48ed68f481908374183c66a6b055 |
completed | May 8, 2026, 2:22 a.m. |
Created at: April 28, 2026, 3:09 p.m.