Triple
T37554400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Judgement Legplates |
E933659
|
entity |
| Predicate | visualCohesionWith |
P69911
|
FINISHED |
| Object | Judgement Crown |
—
|
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: Judgement Crown | Statement: [Judgement Legplates, visualCohesionWith, Judgement Crown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visualCohesionWith Context triple: [Judgement Legplates, visualCohesionWith, Judgement Crown]
-
A.
visualContinuityWith
Indicates that two visual elements are connected in a way that preserves a consistent appearance or flow across them.
-
B.
visualSimplicity
Indicates that something is characterized by a minimal, uncluttered, and easy-to-perceive visual appearance or design.
-
C.
internalCohesion
Indicates the degree to which elements within a group, system, or structure are mutually connected and unified, resisting fragmentation or internal conflict.
-
D.
visualCompanion
chosen
Indicates that one entity serves as a visual counterpart, partner, or accompanying element to another in a visual context.
-
E.
visualizedIn
Indicates that something is represented or depicted within a particular visual medium, view, or visualization.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb9e8108c8190ae1c7940b1677e95 |
completed | May 6, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fbb141605c8190b9c27d70352522db |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.