Triple
T34971765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Honesty |
E1008554
|
entity |
| Predicate | isValuedIn |
P21465
|
FINISHED |
| Object | personal relationships |
—
|
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: personal relationships | Statement: [Honesty, isValuedIn, personal relationships]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isValuedIn Context triple: [Honesty, isValuedIn, personal relationships]
-
A.
isValuedFor
Indicates that one entity is appreciated, esteemed, or considered important because of a particular quality, contribution, or characteristic it provides to another entity.
-
B.
valuesIn
Indicates that one entity specifies or constrains the set of permissible values for another entity.
-
C.
valuedBy
chosen
Indicates that one entity is regarded as important, useful, or held in high esteem by another entity.
-
D.
embodiesValue
Indicates that an entity exemplifies, represents, or gives concrete form to a particular value, principle, or ideal.
-
E.
isSingleValuedOn
Indicates that for each element in the specified domain, the relation associates at most one corresponding value in the codomain.
- 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_69f76dc78a308190a1ac29ad4a9a4895 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.