Triple
T20439060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 79th Street (IRT Broadway–Seventh Avenue Line) |
E501333
|
entity |
| Predicate | hasOrnamentalTrimLine |
P113786
|
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: [79th Street (IRT Broadway–Seventh Avenue Line), hasOrnamentalTrimLine, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOrnamentalTrimLine Context triple: [79th Street (IRT Broadway–Seventh Avenue Line), hasOrnamentalTrimLine, yes]
-
A.
hasTrimLineColor
Indicates that an entity has a specific color applied to the trim or outline portion of its visual representation.
-
B.
hasLiningMaterial
Indicates that one entity uses or contains another entity as the material forming its inner lining.
-
C.
hasTrimMaterial
chosen
Indicates that one entity uses or features a particular material specifically for its trim or edging components.
-
D.
isLinedWith
Indicates that one object or surface is covered, edged, or internally coated along its length or area with another material or layer.
-
E.
hasStripePattern
Indicates that one entity exhibits a stripe-like visual pattern on its surface or body.
- 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_69e0b4ab3cfc8190ac9bf32e932316b1 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e685f112e48190a3af818c0f6ee839 |
completed | April 20, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69e5766df0008190a73c4f613c29678f |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:31 a.m.