Triple
T5384635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Borough Market |
E113172
|
entity |
| Predicate | hasTypeOfStalls |
P62931
|
FINISHED |
| Object | fruit and vegetable stalls |
—
|
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: fruit and vegetable stalls | Statement: [Borough Market, hasTypeOfStalls, fruit and vegetable stalls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfStalls Context triple: [Borough Market, hasTypeOfStalls, fruit and vegetable stalls]
-
A.
hasStalls
Indicates that an entity contains, provides, or is equipped with stalls (e.g., booths, compartments, or vendor stands).
-
B.
numberOfStalls
Indicates the quantity of stalls associated with or contained within a given entity or location.
-
C.
hasStabling
Indicates that one entity provides or contains stabling facilities (such as stalls or accommodation) for another, typically for animals like horses.
-
D.
hasChoirStalls
Indicates that a location or structure contains or is equipped with choir stalls used for seating members of a choir.
-
E.
hasSideWalls
Indicates that an object or structure possesses side walls as part of its physical configuration.
- 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_69bd4436a1988190af18dcff7fd306b4 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd86f39edc81908e53973cef1bc0f3 |
completed | March 20, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69bd8463a9c88190bd760378f3026180 |
completed | March 20, 2026, 5:31 p.m. |
| PDg | Predicate description generation | batch_69bd853005088190b1b092a9beb090b2 |
completed | March 20, 2026, 5:34 p.m. |
Created at: March 20, 2026, 2:03 p.m.