Triple
T32781528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R27 |
E838366
|
entity |
| Predicate | hasPublicName |
P27536
|
FINISHED |
| Object | Broad Street |
—
|
NE NERFINISHED |
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: Broad Street | Statement: [R27, hasPublicName, Broad Street]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPublicName Context triple: [R27, hasPublicName, Broad Street]
-
A.
hasPublic
Indicates that an entity is accessible or visible to the general public rather than being private or restricted.
-
B.
hasProperName
chosen
Indicates that an entity is associated with a specific proper name used to uniquely identify it.
-
C.
hasNameFunction
Indicates that an entity is associated with a function whose purpose is to provide or determine its name.
-
D.
hasComponentName
Indicates that an entity includes or is associated with a component identified by a specific name.
-
E.
hasNameCharacteristic
Indicates that an entity possesses a specific quality or attribute related to its name.
- 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_69f3493b83f48190be335cd42465cecf |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
Created at: May 1, 2026, 1:14 a.m.