Triple
T32058833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | University St |
E818691
|
entity |
| Predicate | addressRole |
P175820
|
FINISHED |
| Object | component of postal addresses |
—
|
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: component of postal addresses | Statement: [University St, addressRole, component of postal addresses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addressRole Context triple: [University St, addressRole, component of postal addresses]
-
A.
addressesRole
Indicates that one entity directs communication, content, or action specifically toward another entity in its capacity or function as a particular role.
-
B.
addressType
Indicates the specific kind or category of address associated with an entity (e.g., home, work, billing, or shipping).
-
C.
anchorRole
Indicates that one entity serves as a primary or reference role to which other related roles or elements are connected or aligned.
-
D.
addressRepresents
Indicates that one address stands for, corresponds to, or serves as the official representation of another entity or location.
-
E.
houseRole
Indicates the functional role, purpose, or use that a house has within a given context or system.
- 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_69f348fdacec8190b9f74375ca3b2094 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26f27dc8190ae426a3e1573933e |
completed | May 3, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69f6d749e7f081909c8196898c4191ad |
completed | May 3, 2026, 5:04 a.m. |
Created at: May 1, 2026, 12:21 a.m.