Triple
T6507488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Medina Sidonia |
E150046
|
entity |
| Predicate | archivesSignificance |
P428
|
FINISHED |
| Object | important source for Spanish and Andalusian history |
—
|
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: important source for Spanish and Andalusian history | Statement: [House of Medina Sidonia, archivesSignificance, important source for Spanish and Andalusian history]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: archivesSignificance Context triple: [House of Medina Sidonia, archivesSignificance, important source for Spanish and Andalusian history]
-
A.
archivesFocus
Indicates that one entity preserves or stores another entity as a primary subject or area of concentration for future reference or use.
-
B.
significance
chosen
Indicates that one entity holds particular importance, influence, or meaningful impact in relation to another entity or context.
-
C.
hasHistoricalSignificance
Indicates that something possesses notable importance or influence within a historical context or period.
-
D.
reasonForSignificance
Indicates that one entity explains or justifies why another entity is important, notable, or significant.
-
E.
archivesType
Indicates that one entity serves as an archival record or stored version of another entity, specifying the type or category of that archived content.
- 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_69c687ef291081909d437f035eef1cda |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c69f386aa08190bfc8592a92ec6339 |
completed | March 27, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69c68ab714908190aa7c2fbf64078e15 |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:43 p.m.