Triple
T1899791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Córdoba (historical) |
E37664
|
entity |
| Predicate | conqueredIn |
P32947
|
FINISHED |
| Object | 1236 |
—
|
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: 1236 | Statement: [Córdoba (historical), conqueredIn, 1236]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conqueredIn Context triple: [Córdoba (historical), conqueredIn, 1236]
-
A.
conqueredFrom
Indicates that one entity gained control of another entity by taking it from a third party that previously held it.
-
B.
conqueredCity
Indicates that one entity has taken control of a city from another entity, typically through military force or domination.
-
C.
conquestEvent
Indicates an event in which one party gains control over another entity or territory through force or domination.
-
D.
conquestPeriod
Indicates the time span during which one entity successfully subjugates or takes control of another through conquest.
-
E.
wasInvadedBy
Indicates that a place or territory was subjected to an incursion or attack carried out by another entity or group.
- 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_69a8861be7148190a680937ec451a304 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb17181b0819090683c55fd1352cb |
completed | March 7, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69abafe7e7e88190b58c0df59187c0c2 |
completed | March 7, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69abb09b27e88190bff164040fef6d7e |
completed | March 7, 2026, 4:59 a.m. |
Created at: March 4, 2026, 7:35 p.m.