Triple
T14585623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King of Hearts (Disney 1951) |
E342307
|
entity |
| Predicate | roleInCourtScene |
P23470
|
FINISHED |
| Object | judge |
—
|
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: judge | Statement: [King of Hearts (Disney 1951), roleInCourtScene, judge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInCourtScene Context triple: [King of Hearts (Disney 1951), roleInCourtScene, judge]
-
A.
roleAtCourt
Indicates the specific position, function, or status an entity holds within a court or courtly setting.
-
B.
courtRole
chosen
Indicates the specific capacity or position an entity holds within a court proceeding or judicial context.
-
C.
legalCaseRole
Indicates the specific role or capacity an entity holds within a legal case, such as plaintiff, defendant, judge, or attorney.
-
D.
roleInScene
Indicates that an entity participates in a particular scene with a specific role or function within that scene.
-
E.
roleInBrethrenCourt
Indicates that an entity holds a specific position or function within the Brethren Court organization or council.
- 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_69d822ddc0f081909cd8163c7de298cd |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb421bb308190a457425429ef6aa5 |
completed | April 14, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69de656a953481909a4645b004c40de7 |
completed | April 14, 2026, 4:03 p.m. |
Created at: April 10, 2026, 1:24 a.m.