Triple
T21458868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 86th Street (Brooklyn) |
E529415
|
entity |
| Predicate | hasTrimLine |
P113786
|
FINISHED |
| Object | mosaic trim line |
—
|
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: mosaic trim line | Statement: [86th Street (Brooklyn), hasTrimLine, mosaic trim line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrimLine Context triple: [86th Street (Brooklyn), hasTrimLine, mosaic trim line]
-
A.
hasTrimLineColor
Indicates that an entity has a specific color applied to the trim or outline portion of its visual representation.
-
B.
hasLineStructure
Indicates that one entity possesses or exhibits a linear arrangement or organization of its components.
-
C.
hasLineLength
Indicates that one entity has, is characterized by, or is associated with a specific line length value.
-
D.
hasLineCharacter
Indicates that one entity possesses or includes a specific character or symbol that appears within a line of text or sequence.
-
E.
hasTrimMaterial
chosen
Indicates that one entity uses or features a particular material specifically for its trim or edging components.
- 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_69e0c458133481908ae8b41a12c4edec |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9e9ed36c08190a5178b2308aca8da |
completed | April 23, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_69e631df1b38819088d3604854e697b4 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:08 p.m.