Triple
T32636546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Judge Nahar |
E834357
|
entity |
| Predicate | parallelsWith |
P57196
|
FINISHED |
| Object | Tiamat |
—
|
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: Tiamat | Statement: [Judge Nahar, parallelsWith, Tiamat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parallelsWith Context triple: [Judge Nahar, parallelsWith, Tiamat]
-
A.
parallels
Indicates that one entity runs alongside or corresponds to another in a way that maintains a consistent separation or similarity without intersecting.
-
B.
structureParallels
Indicates that the structural organization or arrangement of one entity closely corresponds to or mirrors that of another.
-
C.
nowLargelyParalleledBy
Indicates that something has been mostly matched or replicated by something else in function, scope, or effect.
-
D.
parallelType
Indicates that one entity runs in parallel to another, specifying the type or manner of their parallel relationship.
-
E.
hasConceptualParallel
chosen
Indicates that one entity corresponds to or mirrors another at a conceptual level, showing a similar idea, structure, or pattern despite possible differences in form or context.
- 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_69f3492dc2308190a88c6e30a3f3f576 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c775d6188190b236fc4f89a11b61 |
completed | May 3, 2026, 3:56 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f617c08190a70ba880210f908c |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:07 a.m.