Triple
T22493019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Casa de Alba |
E556063
|
entity |
| Predicate | hasInfluencePeriod |
P97182
|
FINISHED |
| Object | late Middle Ages |
—
|
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: late Middle Ages | Statement: [Casa de Alba, hasInfluencePeriod, late Middle Ages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInfluencePeriod Context triple: [Casa de Alba, hasInfluencePeriod, late Middle Ages]
-
A.
hadPeakInfluencePeriod
Indicates the time span during which an entity exerted its greatest or most significant influence.
-
B.
hasInfluenceScope
Indicates the range or extent within which an entity’s influence, impact, or authority is effective or applicable.
-
C.
hasInfluentialStatus
Indicates that an entity holds a position, role, or condition that gives it significant influence or impact over others or over outcomes.
-
D.
appearsInTimePeriod
chosen
Indicates that an entity is present, active, or occurs within a specified time period.
-
E.
hasEraInfluence
Indicates that one era or time period has a significant impact on shaping the characteristics, developments, or outcomes of another.
- 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_69e11e5445bc8190b6a9481926db3355 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15cb01b3481908a9143503b75167f |
completed | April 29, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69e898be31448190be5ae7f5656f0497 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:49 p.m.