Triple
T30519558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | al-Nasir li-Din Allah |
E776656
|
entity |
| Predicate | linkedRulerBirthPlace |
P58095
|
FINISHED |
| Object | Córdoba |
—
|
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: Córdoba | Statement: [al-Nasir li-Din Allah, linkedRulerBirthPlace, Córdoba]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedRulerBirthPlace Context triple: [al-Nasir li-Din Allah, linkedRulerBirthPlace, Córdoba]
-
A.
isBirthplaceRelatedTo
chosen
Indicates that there is a relationship between an entity and a birthplace, such as being born there or otherwise closely associated with that place of birth.
-
B.
nearBirthplaceOf
Indicates that one entity is located close to the place where another entity was born.
-
C.
containsBirthplaceTown
Indicates that one entity includes or specifies the town where another entity was born.
-
D.
hasNamesakeBirthPlace
Indicates that the place is the birthplace of another entity after which the subject entity is named.
-
E.
namedForPersonBornInArea
Indicates that something is named after a person who was born in the specified geographic area.
- 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_69f2249b23c4819087fa85496d92f43f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: April 29, 2026, 8:17 p.m.