Triple
T38389712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Without You |
E899679
|
entity |
| Predicate | positionInPlot |
P201887
|
FINISHED |
| Object | near the end of My Fair Lady |
—
|
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: near the end of My Fair Lady | Statement: [Without You, positionInPlot, near the end of My Fair Lady]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInPlot Context triple: [Without You, positionInPlot, near the end of My Fair Lady]
-
A.
chartPosition
Indicates the ranking or placement of an item within an ordered chart or list at a specific point in time.
-
B.
positionInFrame
Indicates the spatial location or coordinates of an entity within a specific frame or reference image.
-
C.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
-
D.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
-
E.
positionInShow
Indicates the specific order or placement an entity occupies within a show, series, or sequence of performances or episodes.
- 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_69f76e5c9b808190b486523f5c2f817d |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a002e71bdc48190b922f2d3b362d259 |
completed | May 10, 2026, 7:06 a.m. |
| PD | Predicate disambiguation | batch_6a002e1a28708190b65f9e657c770bab |
completed | May 10, 2026, 7:04 a.m. |
| PDg | Predicate description generation | batch_6a002e706dfc8190bbf2bc230f537e83 |
completed | May 10, 2026, 7:06 a.m. |
Created at: May 3, 2026, 4:31 p.m.