Triple
T30816498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 145th Street (IRT Broadway–Seventh Avenue Line) |
E784791
|
entity |
| Predicate | hasMosaicTrim |
P44624
|
FINISHED |
| Object | original IRT-style mosaics |
—
|
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: original IRT-style mosaics | Statement: [145th Street (IRT Broadway–Seventh Avenue Line), hasMosaicTrim, original IRT-style mosaics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMosaicTrim Context triple: [145th Street (IRT Broadway–Seventh Avenue Line), hasMosaicTrim, original IRT-style mosaics]
-
A.
hasMosaic
chosen
Indicates that one entity possesses, contains, or is decorated with a mosaic.
-
B.
hasTrimMaterial
Indicates that one entity uses or features a particular material specifically for its trim or edging components.
-
C.
hasMosaicsBy
Indicates that something contains or features mosaics that were created by a specified agent or creator.
-
D.
hasMosaicSubject
Indicates that something is the depicted subject or main theme represented within a mosaic.
-
E.
hasTrimLineColor
Indicates that an entity has a specific color applied to the trim or outline portion of its visual representation.
- 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_69f224b4eda48190bd212ce4f3901e56 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd64bc86848190a49f451a8fc5cf1e |
completed | May 8, 2026, 4:21 a.m. |
| PD | Predicate disambiguation | batch_69fd5ff4a648819090756d90fd195d9a |
completed | May 8, 2026, 4 a.m. |
Created at: April 29, 2026, 8:44 p.m.