Triple
T25017546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Czech Republic–Austria border |
E626179
|
entity |
| Predicate | cameIntoExistenceInCurrentForm |
P29675
|
FINISHED |
| Object | 1993 |
—
|
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: 1993 | Statement: [Czech Republic–Austria border, cameIntoExistenceInCurrentForm, 1993]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cameIntoExistenceInCurrentForm Context triple: [Czech Republic–Austria border, cameIntoExistenceInCurrentForm, 1993]
-
A.
modeOfEmergence
Indicates the manner or process through which something comes into existence, develops, or arises.
-
B.
beforeBecoming
Indicates that one state, role, or condition existed or occurred prior to another state, role, or condition coming into effect.
-
C.
emergedFrom
Indicates that one entity originated, arose, or came forth from another entity or source.
-
D.
incarnationOf
Indicates that one entity is a concrete embodiment, manifestation, or earthly form of another, typically more abstract or divine, entity.
-
E.
existsSince
chosen
Indicates that an entity has been in existence or valid from a specified point in time onward.
- 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_69e2ff27755881908490178e83701160 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f44ba720748190a16124b842247df2 |
completed | May 1, 2026, 6:43 a.m. |
| PD | Predicate disambiguation | batch_69f442c0c2e88190acd7f170f10ccef6 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 6:06 a.m.