Triple
T36213725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Billingsgate |
E1047629
|
entity |
| Predicate | fishMarketRelocatedTo |
P184776
|
FINISHED |
| Object | Poplar, London |
—
|
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: Poplar, London | Statement: [Billingsgate, fishMarketRelocatedTo, Poplar, London]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fishMarketRelocatedTo Context triple: [Billingsgate, fishMarketRelocatedTo, Poplar, London]
-
A.
fishMarketTypicalClosure
Indicates the usual or characteristic closing time or conditions under which a fish market typically ceases operations.
-
B.
cityFish
Indicates that the subject is a type of fish that inhabits or is commonly found in a particular city.
-
C.
nearbyFishery
Indicates that a fishery is located close to or within a short distance of a specified reference point or area.
-
D.
fishPassage
Indicates that a water structure or feature allows fish to move or migrate through or past it.
-
E.
fishingPort
Indicates that a location functions as a port primarily used for fishing activities, such as landing, processing, or servicing fishing vessels.
- 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_69f76e4214748190a76c986d2a1838c2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b5f89c5c8190825ed5d4317c540c |
completed | May 3, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c44390819084fb5558b354658f |
completed | May 3, 2026, 8:49 p.m. |
| PDg | Predicate description generation | batch_69f7b57aa0848190a22c31c3ff90e0ab |
completed | May 3, 2026, 8:52 p.m. |
Created at: May 3, 2026, 4:09 p.m.