Triple
T23549717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indifference |
E578004
|
entity |
| Predicate | mayBeEvaluatedAs |
P42940
|
FINISHED |
| Object | morally negative |
—
|
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: morally negative | Statement: [Indifference, mayBeEvaluatedAs, morally negative]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeEvaluatedAs Context triple: [Indifference, mayBeEvaluatedAs, morally negative]
-
A.
evaluatesAs
chosen
Indicates that one entity is judged, interpreted, or assessed as having a particular value, role, or classification in relation to another.
-
B.
mayBeDeclared
Indicates that something has the potential or permission to be formally stated, specified, or announced, but has not necessarily been declared yet.
-
C.
mayBeEqualTo
Indicates that two entities are possibly equal, but their equality is uncertain or not definitively established.
-
D.
supportsEvaluation
Indicates that one entity provides the necessary functionality, resources, or conditions for another entity to be assessed, tested, or evaluated.
-
E.
mayBeAssignedBy
Indicates that an entity has the potential or permission to be assigned by another entity, without asserting that the assignment has actually occurred.
- 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_69e245fa93448190919cb04534560542 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1aecd60a881908c257d9ba67080c8 |
completed | April 29, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69f118afabd88190bd88f49597d120e8 |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:11 p.m.