Triple
T25711528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bevil Senior |
E644744
|
entity |
| Predicate | guidesResolutionOf |
P18444
|
FINISHED |
| Object | The Conscious Lovers |
—
|
NE NERFINISHED |
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: The Conscious Lovers | Statement: [Bevil Senior, guidesResolutionOf, The Conscious Lovers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guidesResolutionOf Context triple: [Bevil Senior, guidesResolutionOf, The Conscious Lovers]
-
A.
resolutionOf
Indicates that one entity is the formal decision, outcome, or solution produced in response to, or for the purpose of addressing, another entity such as an issue, proposal, or problem.
-
B.
resolutionLeadsTo
Indicates that achieving a particular resolution or decision directly brings about or causes a subsequent outcome or state.
-
C.
providesGuidanceTo
chosen
Indicates that one entity offers direction, advice, or instruction to another entity.
-
D.
resolutionIdea
Indicates a proposed method, plan, or approach intended to resolve or address a particular issue, conflict, or problem.
-
E.
resolutionMethod
Indicates the specific approach, technique, or process used to resolve a problem, conflict, or issue.
- 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_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_69f480824a1c81908a8a492eedbc2596 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 9:14 p.m.