Triple
T24474732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daegok-ri |
E617199
|
entity |
| Predicate | timePeriodOfMainSite |
P52643
|
FINISHED |
| Object | prehistoric era |
—
|
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: prehistoric era | Statement: [Daegok-ri, timePeriodOfMainSite, prehistoric era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timePeriodOfMainSite Context triple: [Daegok-ri, timePeriodOfMainSite, prehistoric era]
-
A.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
B.
locationPeriod
Indicates that an entity is associated with being at a particular location during a specified time period.
-
C.
timeBetweenMainEvents
Indicates the duration or interval separating two primary or key events in a sequence or process.
-
D.
timePeriodOfMajorImportance
Indicates that a particular time period holds significant importance or prominence within a given context or domain.
-
E.
timePeriodCategory
chosen
Indicates the classification of a time period into a specific category or type (e.g., era, phase, or temporal grouping).
- 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_69e2d7f197588190889a03e620558059 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29947084081908895573a4a4e4822 |
completed | April 29, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69f287d76c7c81909494f12e606a9149 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:20 a.m.