Triple
T30032437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Catch Me If You Can |
E763057
|
entity |
| Predicate | broadwayBorough |
P40044
|
FINISHED |
| Object | Manhattan |
—
|
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: Manhattan | Statement: [Catch Me If You Can, broadwayBorough, Manhattan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: broadwayBorough Context triple: [Catch Me If You Can, broadwayBorough, Manhattan]
-
A.
broadwayTheatreDistrict
Indicates that something is located in or associated with the Broadway Theatre District, the area known for its concentration of Broadway theaters and related activities.
-
B.
broadwayLocation
Indicates that an entity is located on, near, or associated with Broadway (typically the Broadway theater district or street).
-
C.
preBroadwayCity
Indicates the city where a production was staged or developed prior to its official Broadway run.
-
D.
wasBoroughOf
Indicates that one place previously held the administrative or territorial status of a borough within another jurisdiction.
-
E.
operatedInBorough
chosen
Indicates that an entity conducted its operations or activities within the geographic area of a specific borough.
- 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_69f2246fb2b88190acff36bf7975c8f0 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 6:50 p.m.