Triple
T16317169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dr. Allison Cameron |
E396199
|
entity |
| Predicate | hasStrongEthics |
P122663
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Dr. Allison Cameron, hasStrongEthics, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStrongEthics Context triple: [Dr. Allison Cameron, hasStrongEthics, true]
-
A.
hasEthicalStandard
Indicates that an entity adheres to, follows, or is governed by a specified set of ethical principles or standards.
-
B.
hasEthicalIdeal
Indicates that an entity upholds or is guided by a particular ethical standard, principle, or ideal.
-
C.
hasEthicsBody
Indicates that an entity is associated with, overseen by, or governed through a formal ethics committee or ethics review body.
-
D.
hasCorporateEthos
Indicates that an entity embodies, promotes, or is characterized by a particular set of shared corporate values, principles, and cultural norms.
-
E.
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.
- 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_69d87f255b788190a400eba031dd85d8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e296b31b988190bb1fde36dae11bbd |
completed | April 17, 2026, 8:23 p.m. |
| PD | Predicate disambiguation | batch_69e219fc72c881909d452274e7af8238 |
completed | April 17, 2026, 11:31 a.m. |
| PDg | Predicate description generation | batch_69e21e56e0348190a3d9475360231a70 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:06 a.m.