Triple
T24858226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La busca de Averroes |
E622084
|
entity |
| Predicate | hasImaginedHistoricalFigure |
P53504
|
FINISHED |
| Object | Averroes |
—
|
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: Averroes | Statement: [La busca de Averroes, hasImaginedHistoricalFigure, Averroes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasImaginedHistoricalFigure Context triple: [La busca de Averroes, hasImaginedHistoricalFigure, Averroes]
-
A.
basedOnHistoricalFigure
Indicates that something is derived from, inspired by, or modeled after a real historical person.
-
B.
hasNamesakeRoleInHistory
Indicates that an entity has a historical role or position that is the same as, or named after, another entity’s role in history.
-
C.
usesRealHistoricalFigures
chosen
Indicates that the work includes or depicts actual people from real history rather than entirely fictional characters.
-
D.
historicalFigureDiscussed
Indicates that a historical figure is the topic of discussion, analysis, or commentary in some context.
-
E.
historicalFigure
Indicates that an entity is recognized as a notable person from the past who played a significant role in history.
- 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_69e2fac350d08190b3affde1b451a8c5 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f47b865df48190bf4b6d3e9f9305e6 |
completed | May 1, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69f4682c8a3c8190adbfaac99474eaaf |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 18, 2026, 5:21 a.m.