Triple
T35783208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karfeddion |
E1034489
|
entity |
| Predicate | sectorCapitalOf |
P184657
|
FINISHED |
| Object | Karfeddion system |
—
|
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: Karfeddion system | Statement: [Karfeddion, sectorCapitalOf, Karfeddion system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sectorCapitalOf Context triple: [Karfeddion, sectorCapitalOf, Karfeddion system]
-
A.
departmentCapitalOf
Indicates that a location serves as the administrative capital of a specified department (an administrative division).
-
B.
isFinancialCapitalOf
Indicates that a city or region serves as the primary center for a country’s or area’s financial, banking, and economic market activities.
-
C.
coCapitalOf
Indicates that two or more cities share the status of being capital cities of the same political or administrative entity.
-
D.
capitalFor
Indicates that one entity serves as the capital city or administrative center for another entity, such as a country, state, or region.
-
E.
countryCapitalSector
Indicates that a specified sector or area lies within or corresponds to the capital city of a given country.
- 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_69f76e14a1e081908eddd57bd6fdb3be |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b365288c8190bcb11fcfba028737 |
completed | May 3, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
| PDg | Predicate description generation | batch_69f7b2f2b9ac8190aa05b8a1aa18ec2d |
completed | May 3, 2026, 8:41 p.m. |
Created at: May 3, 2026, 4:06 p.m.