Triple
T24852046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Azdak |
E621913
|
entity |
| Predicate | makesJudgmentIn |
P95569
|
FINISHED |
| Object | child custody dispute over Michael |
—
|
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: child custody dispute over Michael | Statement: [Azdak, makesJudgmentIn, child custody dispute over Michael]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: makesJudgmentIn Context triple: [Azdak, makesJudgmentIn, child custody dispute over Michael]
-
A.
leadingJudgmentBy
Indicates a relationship where one judgment or legal decision is treated as the primary or authoritative basis guiding or influencing another judgment.
-
B.
judgmentInvolves
Indicates that a particular judgment, decision, or legal ruling includes, concerns, or pertains to a specified entity or matter.
-
C.
judgmentResult
Indicates the outcome or decision produced by a judgment, such as a court ruling, evaluation, or formal assessment, regarding the entities involved.
-
D.
judgeInTrial
chosen
Indicates that an entity serves as the judicial authority presiding over and making legal determinations in a specific trial.
-
E.
containsJudgmentIn
Indicates that one entity includes or embeds a specific judgment or decision within it.
- 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_69e2fac297e481909d3aedc75f585e42 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f43043512481909501a3979cac9947 |
completed | May 1, 2026, 4:46 a.m. |
| PD | Predicate disambiguation | batch_69f420fd375c81908ea4a4e60b76ee8f |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:20 a.m.