Triple
T7191909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York State Route 907L |
E167711
|
entity |
| Predicate | signageStatus |
P75663
|
FINISHED |
| Object | not signed for the public |
—
|
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: not signed for the public | Statement: [New York State Route 907L, signageStatus, not signed for the public]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signageStatus Context triple: [New York State Route 907L, signageStatus, not signed for the public]
-
A.
hasSignage
Indicates that appropriate signs or visual markers are present to convey information, directions, warnings, or identification related to the associated entity.
-
B.
signageStandard
Indicates that something conforms to, follows, or specifies a particular standard or convention for signage.
-
C.
hasSignageType
Indicates the specific category or kind of signage associated with an object, location, or entity.
-
D.
hasSignageIn
Indicates that appropriate signs or signage for an entity are present or installed within a specified location or area.
-
E.
hasSignageName
Indicates that an entity has a specific name or label as it appears on its physical signage.
- 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_69c6888b5248819090499a884ee3ec39 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e901ea1481908a9e44f96dd4b553 |
completed | March 27, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69c6e752385c819096fbab55566ee2a8 |
completed | March 27, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69c6e8b5f6508190af28e06a7959d717 |
completed | March 27, 2026, 8:29 p.m. |
Created at: March 27, 2026, 2:50 p.m.