Triple
T27780408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William "Billy" Tyne Jr. |
E699319
|
entity |
| Predicate | fishingPort |
P163344
|
FINISHED |
| Object | Gloucester fishing fleet |
—
|
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: Gloucester fishing fleet | Statement: [William "Billy" Tyne Jr., fishingPort, Gloucester fishing fleet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fishingPort Context triple: [William "Billy" Tyne Jr., fishingPort, Gloucester fishing fleet]
-
A.
isFishingPort
Indicates that a location functions primarily as a port where fishing vessels operate and fish-related activities such as landing, processing, or trading catch take place.
-
B.
nearbyFishery
Indicates that a fishery is located close to or within a short distance of a specified reference point or area.
-
C.
harbours
Indicates that one entity provides shelter, refuge, or concealment for another, often by keeping it safe or hidden.
-
D.
isFishingArea
Indicates that a location or region is designated or used as an area where fishing activities take place.
-
E.
fishingActivity
Indicates an activity where an entity engages in catching or attempting to catch fish or other aquatic organisms.
- 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_69ef6a4b5a9081909c9111396c2be3d2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f637cd6cb88190890704547d681fb2 |
completed | May 2, 2026, 5:43 p.m. |
| PD | Predicate disambiguation | batch_69f6318ae6f08190b3f85f9201046a15 |
completed | May 2, 2026, 5:16 p.m. |
| PDg | Predicate description generation | batch_69f6359d46b88190922dd7de508e3b0e |
completed | May 2, 2026, 5:34 p.m. |
Created at: April 27, 2026, 5:09 p.m.