Triple
T26287229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Granville fishing port |
E661169
|
entity |
| Predicate | mainCatch |
P138274
|
FINISHED |
| Object | scallops |
—
|
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: scallops | Statement: [Granville fishing port, mainCatch, scallops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainCatch Context triple: [Granville fishing port, mainCatch, scallops]
-
A.
catchStyle
Indicates the manner or technique with which something is caught (e.g., how an object, ball, or entity is captured or received).
-
B.
primaryCatch
Indicates that an entity is the main or most significant target, recipient, or object captured or obtained in a given context.
-
C.
hasPrimaryCatch
chosen
Indicates that an entity (such as a fishery, vessel, or fishing activity) has a main or predominant type of catch associated with it.
-
D.
mainRite
Indicates that one ritual, ceremony, or rite is the primary or central rite associated with a given context, entity, or event.
-
E.
mainCase
Indicates that one case is the primary or central case associated with an entity or context, distinguishing it from other related cases.
- 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_69ee812bbd448190be4d7478b057990a |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 26, 2026, 10:05 p.m.