Triple
T8821634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lady Justice |
E209917
|
entity |
| Predicate | toolRepresents |
P39361
|
FINISHED |
| Object | scales represent weighing of evidence |
—
|
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: scales represent weighing of evidence | Statement: [Lady Justice, toolRepresents, scales represent weighing of evidence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: toolRepresents Context triple: [Lady Justice, toolRepresents, scales represent weighing of evidence]
-
A.
toolDescribed
Indicates that one entity provides a description or explanation of a tool associated with another entity.
-
B.
componentRepresents
chosen
Indicates that one component stands in for, symbolizes, or models another entity or concept within a system or context.
-
C.
depictsTool
Indicates that one entity visually represents or shows a tool in some form of depiction (e.g., an image, illustration, or artwork).
-
D.
toolIn
Indicates that one entity is a tool or instrument used in or associated with another entity or context.
-
E.
toolUsed
Indicates that an action or task is performed using a particular tool as the means or instrument.
- 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_69ca8364e13081909c85fe80f44fe86f |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc601126248190b6f10c22f1aeac9a |
completed | April 1, 2026, midnight |
| PD | Predicate disambiguation | batch_69cc5c21e64c81908490e3b0875dc0d6 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:46 p.m.