Triple
T28166467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | former Great Mosque of Málaga |
E715338
|
entity |
| Predicate | functionedUntilEvent |
P168616
|
FINISHED |
| Object | Christian conquest of Málaga |
—
|
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: Christian conquest of Málaga | Statement: [former Great Mosque of Málaga, functionedUntilEvent, Christian conquest of Málaga]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionedUntilEvent Context triple: [former Great Mosque of Málaga, functionedUntilEvent, Christian conquest of Málaga]
-
A.
functionedBefore
Indicates that one entity was operational or in working order at an earlier time than another entity.
-
B.
diesBeforeEvent
Indicates that the subject entity dies at a point in time that occurs before the specified event takes place.
-
C.
succeededByEvent
Indicates that one event directly follows and replaces another in a temporal or sequential order.
-
D.
usedAfterEventFor
Indicates that one entity is used only after a specified event has occurred or been completed.
-
E.
maintainedAfterEvent
Indicates that a state, condition, or relationship continues to hold true after a specified event has occurred.
- 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_69efd6b340f0819095680e15dcdc1830 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f67595fa7c8190b6e9f7a8c700dd97 |
completed | May 2, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f674df80b08190adb7f7531083bbb1 |
completed | May 2, 2026, 10:04 p.m. |
Created at: April 27, 2026, 10:10 p.m.