Triple
T33118446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dorian |
E847522
|
entity |
| Predicate | hasEthicalSubroutines |
P184028
|
FINISHED |
| Object | Yes |
—
|
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: Yes | Statement: [Dorian, hasEthicalSubroutines, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEthicalSubroutines Context triple: [Dorian, hasEthicalSubroutines, Yes]
-
A.
hasEthicalConstraint
Indicates that an entity is subject to a specified ethical rule, limitation, or normative requirement that governs its behavior or decisions.
-
B.
hasEthicalConstraints
Indicates that an entity is subject to specific moral or ethical rules that govern or limit its actions or decisions.
-
C.
hasEthicalRole
Indicates that an entity holds a position, function, or responsibility defined in terms of ethical duties, norms, or moral obligations in relation to another entity or context.
-
D.
hasEthicalBasisIn
Indicates that the ethical justification, grounding, or normative foundation of one entity is derived from, supported by, or based upon another entity.
-
E.
hasEthicalDimension
Indicates that the relationship, action, or situation involves moral considerations, value judgments, or ethical implications.
- F. None of above. chosen
Provenance (4 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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7aaabb58c8190bf81673608ecfb6e |
completed | May 3, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f7aa6795f481908940838ee7041ff5 |
completed | May 3, 2026, 8:04 p.m. |
Created at: May 1, 2026, 1:27 a.m.