Triple
T12106566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harry Hope’s saloon |
E288316
|
entity |
| Predicate | stageDirectionsDescribeAs |
P70609
|
FINISHED |
| Object | dilapidated |
—
|
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: dilapidated | Statement: [Harry Hope’s saloon, stageDirectionsDescribeAs, dilapidated]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stageDirectionsDescribeAs Context triple: [Harry Hope’s saloon, stageDirectionsDescribeAs, dilapidated]
-
A.
stageDirectionDescription
chosen
Indicates a textual description of how an action, movement, or expression should be performed or presented within a staged or scripted context.
-
B.
styleDescribedAs
Indicates that the manner, aesthetic, or mode of something is characterized or labeled using a particular style description.
-
C.
describes
Indicates that one entity provides an explanation, representation, or account of another entity or concept.
-
D.
describedIn
Indicates that information about an entity is contained or documented within a specified source, such as a text, document, or media.
-
E.
stageName
Indicates that one entity is the performance or professional name used by another 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_69d6ab4a5c448190a110d1273314b21a |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9164ada5081908676bd9e5947268a |
completed | April 10, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69d9150497408190921334d21503375a |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:49 p.m.