Triple
T19529789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gyeongju Historic Areas |
E488626
|
entity |
| Predicate | startOfCapitalFunction |
P32945
|
FINISHED |
| Object | 57 BCE |
—
|
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: 57 BCE | Statement: [Gyeongju Historic Areas, startOfCapitalFunction, 57 BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startOfCapitalFunction Context triple: [Gyeongju Historic Areas, startOfCapitalFunction, 57 BCE]
-
A.
hasCapitalFunction
Indicates that an entity serves as the primary seat of government or main administrative center for another entity.
-
B.
capitalizedOn
Indicates that one entity took advantage of, exploited, or made beneficial use of an opportunity, situation, or resource provided or created by another entity.
-
C.
startPointIsCapitalOf
Indicates that the starting point in a relation or path is a city that serves as the capital of the relevant region, country, or administrative entity.
-
D.
timeAsCapitalStart
chosen
Indicates the point in time when a location first became the capital of a political or administrative entity.
-
E.
precededByCapital
Indicates that the referenced element is immediately preceded by a capital letter.
- 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_69d8e8da8bec819081f400199491ccc3 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6363dfd6c8190aaa0b374184965bb |
completed | April 20, 2026, 2:20 p.m. |
| PD | Predicate disambiguation | batch_69e514c9c00481909b76bda67957e58b |
completed | April 19, 2026, 5:45 p.m. |
Created at: April 10, 2026, 1:41 p.m.