Triple
T30888025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polly Sherman |
E786819
|
entity |
| Predicate | oftenResolves |
P9755
|
FINISHED |
| Object | hotel crises |
—
|
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: hotel crises | Statement: [Polly Sherman, oftenResolves, hotel crises]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenResolves Context triple: [Polly Sherman, oftenResolves, hotel crises]
-
A.
resolves
chosen
Indicates that one entity successfully finds a solution, answer, or outcome for a problem, conflict, or uncertainty involving another entity.
-
B.
oftenSucceeded
Indicates that one entity frequently or repeatedly follows another in a sequence of successes or outcomes.
-
C.
oftenFrom
Indicates that something frequently originates, derives, or comes from a particular source or location.
-
D.
resolvesOver
Indicates that one entity successfully addresses, settles, or overcomes an issue, conflict, or obstacle involving another entity or context.
-
E.
notResolvedBy
Indicates that an issue, problem, or request remains unresolved despite the involvement or actions of a specified entity.
- 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_69f224bbfa7c81908448e0c261c523e3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7b2f3a104819098ddd8909eaf596c |
completed | May 3, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
Created at: April 29, 2026, 8:49 p.m.