Triple
T4839097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Tombs of the Joseon Dynasty |
E108133
|
entity |
| Predicate | coreZoneArea |
P59696
|
FINISHED |
| Object | 183.7 ha |
—
|
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: 183.7 ha | Statement: [Royal Tombs of the Joseon Dynasty, coreZoneArea, 183.7 ha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreZoneArea Context triple: [Royal Tombs of the Joseon Dynasty, coreZoneArea, 183.7 ha]
-
A.
coreAreaOf
Indicates that one entity is the central, primary, or most important area or domain of focus for another entity.
-
B.
zone
Indicates that an entity is located within, associated with, or assigned to a particular geographic or conceptual area or zone.
-
C.
cityArea
Indicates the total geographic area covered by a city.
-
D.
coreRegionOf
Indicates that one entity constitutes the central or most essential part of another entity’s structure, area, or domain.
-
E.
metroArea
Indicates that one location is part of, or belongs to, a specified metropolitan area.
- 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_69bd43fbe444819085cb970706ef73f7 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6e01872c81909607010c10538ad1 |
completed | March 20, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69bd6c2375a4819098e16acb982c8fab |
completed | March 20, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69bd6dfff1488190a32bbb615bfab970 |
completed | March 20, 2026, 3:55 p.m. |
Created at: March 20, 2026, 1:25 p.m.