Triple
T24858220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La busca de Averroes |
E622084
|
entity |
| Predicate | hasAuthorialIntrusion |
P157765
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [La busca de Averroes, hasAuthorialIntrusion, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAuthorialIntrusion Context triple: [La busca de Averroes, hasAuthorialIntrusion, true]
-
A.
hasAuthorialStance
Indicates that an entity expresses, embodies, or is associated with a particular author’s viewpoint, attitude, or perspective toward its subject matter.
-
B.
hasAuthorialBackground
Indicates that an entity has a creator or author with a specific background, context, or set of characteristics associated with them.
-
C.
hasAuthorNote
Indicates that an entity includes or is associated with a specific author-provided note or commentary.
-
D.
intrudedInto
Indicates that one entity has entered or encroached upon another entity’s space, domain, or context without permission or in an unwelcome manner.
-
E.
hasAuthorAtTimeOfWriting
Indicates that a work is associated with a specific author as they were at the particular time the work was written.
- F. None of above. chosen
Provenance (4 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_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442b8479c8190a7c8e416ac9e28a0 |
completed | May 1, 2026, 6:05 a.m. |
| PDg | Predicate description generation | batch_69f44a3adb7c8190941572f718b3b93c |
completed | May 1, 2026, 6:37 a.m. |
Created at: April 18, 2026, 5:21 a.m.