Triple
T421679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Albany–Rensselaer rail bridge |
E8115
|
entity |
| Predicate | isPartOfCategory |
P87
|
FINISHED |
| Object | railway bridges in New York State |
—
|
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: railway bridges in New York State | Statement: [Albany–Rensselaer rail bridge, isPartOfCategory, railway bridges in New York State]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfCategory Context triple: [Albany–Rensselaer rail bridge, isPartOfCategory, railway bridges in New York State]
-
A.
isPartOfType
Indicates that one type or category is a constituent or subset within a larger, encompassing type or category.
-
B.
hasPartIn
Indicates that an entity participates in or plays a role within a larger event, process, or composite entity.
-
C.
isPartOfStandard
Indicates that something belongs to, is included within, or conforms to a defined standard or standardized set.
-
D.
hasPart
Indicates that one entity is a component, segment, or constituent part of another entity.
-
E.
category
chosen
Indicates that one entity is classified as a member or type within the grouping or class defined by another entity.
- 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_69a2e7f1d1bc81909cf2dc9754a3c334 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eec0e9dc81908c08b209ce5278ef |
completed | Feb. 28, 2026, 1:33 p.m. |
| PD | Predicate disambiguation | batch_69a2edd3b948819097d96c73d0a0f699 |
completed | Feb. 28, 2026, 1:29 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.