Triple
T28590706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 73 Tremont Street |
E723632
|
entity |
| Predicate | street address |
P606
|
FINISHED |
| Object | 73 Tremont Street |
—
|
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: 73 Tremont Street | Statement: [73 Tremont Street, street address, 73 Tremont Street]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: street address Context triple: [73 Tremont Street, street address, 73 Tremont Street]
-
A.
streetAddress
chosen
Indicates the specific location of an entity in terms of its numbered building and street name within a postal address.
-
B.
address
Indicates that one entity directs spoken or written communication specifically to another entity.
-
C.
streetLocation
Indicates that one entity is located on, along, or at a specific street associated with the other entity.
-
D.
locationAddressed
Indicates that a communication, message, or action is specifically directed to or intended for a particular location or address.
-
E.
streetAddressSuffix
Indicates the trailing component of a street address, such as a directional or unit/lot/apartment designator that follows the main street address.
- 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_69f01d7f92e481909847f5f3f3174a89 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f65876c52c8190bc889c7a67bd07f3 |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 4:20 a.m.