Triple
T4167865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kiss of the Spider Woman |
E84486
|
entity |
| Predicate | hasWestEndRun |
P54465
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Kiss of the Spider Woman, hasWestEndRun, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWestEndRun Context triple: [Kiss of the Spider Woman, hasWestEndRun, yes]
-
A.
hasRunwaySide
Indicates that a runway is located on or associated with a particular side or boundary of another feature (such as an airport or airfield area).
-
B.
hasRunwayCount
Indicates the number of runways that a given entity (such as an airport) possesses.
-
C.
hasRunwayExtension
Indicates that a runway has an additional extended section beyond its original length.
-
D.
usesRunwayOf
Indicates that one entity makes use of the runway that belongs to or is associated with another entity.
-
E.
hasEnd
Indicates that one entity serves as the terminal point, boundary, or conclusion of another entity or process.
- 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_69aed932cab48190b80ffe35f7029ae1 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af02c573788190a60ab3f83b07a6f6 |
completed | March 9, 2026, 5:26 p.m. |
| PD | Predicate disambiguation | batch_69af018fb0948190a9701b2e8e5d9bac |
completed | March 9, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69af01ee94ec8190aa6dde54d4571c04 |
completed | March 9, 2026, 5:22 p.m. |
Created at: March 9, 2026, 3:44 p.m.