Triple
T35747868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bond Passage |
E1033235
|
entity |
| Predicate | hasNameOriginSimilarTo |
P106359
|
FINISHED |
| Object | Bond 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: Bond Street | Statement: [Bond Passage, hasNameOriginSimilarTo, Bond Street]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameOriginSimilarTo Context triple: [Bond Passage, hasNameOriginSimilarTo, Bond Street]
-
A.
hasNameOrigin
Indicates that the origin or source of an entity’s name is specified by the related entity.
-
B.
hasNameOriginType
Indicates that there is a specific type or category describing the origin of an entity’s name.
-
C.
hasGivenNameCounterpart
Indicates that one entity is the given-name (first-name) counterpart or variant of another entity, typically linking related personal names.
-
D.
hasNameEtymologyIn
Indicates that the origin or derivation of an entity’s name is based in, or traceable to, a specified source such as a language, place, or cultural context.
-
E.
namedForSimilarityTo
chosen
Indicates that one entity is given its name because of a perceived resemblance or likeness to 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_69f76e119d508190a3873cb302063832 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff5b233e9c8190adc06cca0758986b |
completed | May 9, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69ff5a5682108190a006b23c4fcdcc7c |
completed | May 9, 2026, 4:01 p.m. |
Created at: May 3, 2026, 4:06 p.m.