Triple
T25711534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bevil Senior |
E644744
|
entity |
| Predicate | embodiesValue |
P159490
|
FINISHED |
| Object | prudence |
—
|
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: prudence | Statement: [Bevil Senior, embodiesValue, prudence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: embodiesValue Context triple: [Bevil Senior, embodiesValue, prudence]
-
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.
supportsValue
Indicates that one entity provides justification, evidence, or backing for the truth, relevance, or appropriateness of a particular value associated with another entity.
-
C.
valueExpressed
Indicates that a particular value, opinion, or quantitative measure is articulated, represented, or made explicit by an entity or expression.
-
D.
value1CorrespondsTo
Indicates that one value is directly associated with, matches, or maps to another value in a defined correspondence.
-
E.
valuesIn
Indicates that one entity specifies or constrains the set of permissible values for another entity.
- 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_69e77e83c8ec8190bf52fcdac4838984 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fc157d9c819096b30f09438e351a |
completed | May 2, 2026, 1:28 p.m. |
| PD | Predicate disambiguation | batch_69f4a0f7c6008190ae8cee3e71e19b94 |
completed | May 1, 2026, 12:47 p.m. |
| PDg | Predicate description generation | batch_69f55e497fa081909bc59a7b92c5df59 |
completed | May 2, 2026, 2:15 a.m. |
Created at: April 21, 2026, 9:14 p.m.