Triple
T8833718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Romania–Ukraine maritime boundary case |
E210209
|
entity |
| Predicate | dateJudgment |
P35640
|
FINISHED |
| Object | 2009-02-03 |
—
|
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: 2009-02-03 | Statement: [Romania–Ukraine maritime boundary case, dateJudgment, 2009-02-03]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateJudgment Context triple: [Romania–Ukraine maritime boundary case, dateJudgment, 2009-02-03]
-
A.
decisionDate
Indicates the date on which a specific decision was formally made or finalized.
-
B.
trialDate
Indicates the specific calendar date on which a legal trial or court proceeding is scheduled or took place.
-
C.
judgmentInvolves
Indicates that a particular judgment, decision, or legal ruling includes, concerns, or pertains to a specified entity or matter.
-
D.
appealDate
Indicates the date on which an appeal is formally filed, recorded, or scheduled in relation to a decision or case.
-
E.
dateOfLastJudgment
chosen
Indicates the specific date on which the most recent formal judgment or decision was rendered in a given case or proceeding.
- 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_69ca8388549c819095fd94eadefbb007 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc60670fa48190b2a873f6498de7f6 |
completed | April 1, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69cc5c23d08481908d8c9b0ad3d1dc00 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:47 p.m.