Triple
T38426676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Staindrop |
E903377
|
entity |
| Predicate | traditionalMainStreet |
P461
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Staindrop, traditionalMainStreet, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalMainStreet Context triple: [Staindrop, traditionalMainStreet, true]
-
A.
traditionalInCity
Indicates that something is customary, long-established, or historically rooted within a particular city.
-
B.
traditionalDistrict
Indicates that an entity is located in, associated with, or belongs to a historically recognized or customary administrative or cultural district.
-
C.
hasMainStreet
chosen
Indicates that a place or locality possesses a primary street commonly recognized as its main thoroughfare.
-
D.
centralStreet
Indicates that a street serves as the main or most important thoroughfare within a given area or settlement.
-
E.
traditionalHomeVenueCity
Indicates the city that has historically served as the primary home venue location for an entity, such as a team or performer.
- 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_69f76e67e4fc8190a7d08dfe9a8af998 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a000a1d8fa88190a1d82ac746565c48 |
completed | May 10, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_6a0008b26eb88190ae03b2309a614774 |
completed | May 10, 2026, 4:25 a.m. |
Created at: May 3, 2026, 4:31 p.m.