Triple
T33361585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mayport shrimping fleet |
E854236
|
entity |
| Predicate | usesGearType |
P2728
|
FINISHED |
| Object | trawl nets |
—
|
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: trawl nets | Statement: [Mayport shrimping fleet, usesGearType, trawl nets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesGearType Context triple: [Mayport shrimping fleet, usesGearType, trawl nets]
-
A.
hasRunningGear
Indicates that an entity is equipped with or possesses running gear, such as the mechanical components that enable movement or operation.
-
B.
usesEquipment
chosen
Indicates that an entity employs or operates a particular piece of equipment to perform an action or fulfill a function.
-
C.
typicalGear
Indicates that the object represents the usual or standard equipment or gear commonly associated with the subject.
-
D.
usesGearboxFrom
Indicates that one entity operates or functions using a gearbox that originates from or is supplied by another entity.
-
E.
hasArrestingGear
Indicates that an entity is equipped with a system or mechanism used to rapidly decelerate and stop another entity, typically during landing or capture.
- 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_69f3496bda8c8190bfc8fade9d1b791c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e3156ea48190b604e414665ef351 |
completed | May 3, 2026, 5:54 a.m. |
| PD | Predicate disambiguation | batch_69f6de0b9ba48190887c9eb5d06a2e94 |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:34 a.m.