Triple
T24379687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beomseo-eup |
E614572
|
entity |
| Predicate | appliesLocalLawOf |
P120344
|
FINISHED |
| Object | Ulsan Metropolitan City |
—
|
NE NERFINISHED |
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: Ulsan Metropolitan City | Statement: [Beomseo-eup, appliesLocalLawOf, Ulsan Metropolitan City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesLocalLawOf Context triple: [Beomseo-eup, appliesLocalLawOf, Ulsan Metropolitan City]
-
A.
appliesLocalLaw
chosen
Indicates that a legal rule, decision, or authority is governed by and enforced under the laws of a specific local jurisdiction.
-
B.
appliesLawThrough
Indicates that one entity enforces, implements, or carries out a law or legal rule by means of another entity or mechanism.
-
C.
stateLawAppliesFrom
Indicates that a particular state law becomes applicable starting from a specified point in time or under certain conditions.
-
D.
localLawRepresentedBy
Indicates that a specific local law is formally represented, expressed, or captured by a particular legal document, code section, or representation.
-
E.
legalCodeAppliesTo
Indicates that a particular legal code or statute is applicable to, or governs, a specified subject, situation, or entity.
- 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_69e2d7e362e481909e32fe4ef8269d4f |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f293da489c81909a7912b790be8b8a |
completed | April 29, 2026, 11:27 p.m. |
| PD | Predicate disambiguation | batch_69f287c4a2b48190b80fb7a3c0e9b018 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:03 a.m.