Triple
T30516642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Angel Peacock |
E776584
|
entity |
| Predicate | traditionLanguage |
P151529
|
FINISHED |
| Object | Kurdish |
—
|
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: Kurdish | Statement: [Angel Peacock, traditionLanguage, Kurdish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionLanguage Context triple: [Angel Peacock, traditionLanguage, Kurdish]
-
A.
languageTraditionally
chosen
Indicates that something is customarily or historically expressed, written, or communicated in a particular language.
-
B.
traditionalLanguageName
Indicates the name traditionally used in a particular language to refer to the subject entity.
-
C.
laterTraditionsLanguage
Indicates that later traditions or sources refer to or describe the subject using the specified language.
-
D.
languageFamilyTraditional
Indicates that one entity belongs to, or is classified under, the traditional language family of the other entity.
-
E.
languageTraditions
Indicates that there is a relationship between entities involving the customs, practices, and conventions associated with the use, preservation, or transmission of a particular language.
- 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_69fddd373cdc8190be1b12e70e4deb1f |
completed | May 8, 2026, 12:55 p.m. |
| PD | Predicate disambiguation | batch_69fddc6915a88190ad41e379aa3ede13 |
completed | May 8, 2026, 12:51 p.m. |
Created at: April 29, 2026, 8:16 p.m.