Triple
T19529790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gyeongju Historic Areas |
E488626
|
entity |
| Predicate | endOfCapitalFunction |
P136661
|
FINISHED |
| Object | 935 CE |
—
|
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: 935 CE | Statement: [Gyeongju Historic Areas, endOfCapitalFunction, 935 CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endOfCapitalFunction Context triple: [Gyeongju Historic Areas, endOfCapitalFunction, 935 CE]
-
A.
endOf
Indicates that one entity marks the terminating point or final boundary of another entity, event, or interval.
-
B.
hasCapitalAtEnd
Indicates that the capital or uppercase letter appears at the end of the given string or sequence.
-
C.
endOfState
Indicates the point or condition at which a particular state, situation, or process comes to an end.
-
D.
functionEnd
Indicates the point or condition at which a function, process, or operation terminates or completes.
-
E.
endName
Indicates that one entity serves as the ending or final name/designation associated with another entity.
- 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_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. |
| PDg | Predicate description generation | batch_69e51a23300c8190988552491d9783d7 |
completed | April 19, 2026, 6:08 p.m. |
Created at: April 10, 2026, 1:41 p.m.