Triple
T13019000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Camargue cowboys |
E322626
|
entity |
| Predicate | traditionalEquipment |
P59326
|
FINISHED |
| Object | trident |
—
|
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: trident | Statement: [Camargue cowboys, traditionalEquipment, trident]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalEquipment Context triple: [Camargue cowboys, traditionalEquipment, trident]
-
A.
typeOfEquipmentUsed
Indicates that a particular piece or category of equipment is utilized in performing a specific action, process, or activity.
-
B.
traditionalKit
chosen
Indicates that an entity is a conventional or customary set of tools, equipment, or components used together for a particular purpose.
-
C.
primaryEquipment
Indicates that one entity serves as the main or most important piece of equipment used by another entity.
-
D.
traditionalMaterial
Indicates that something is made from, incorporates, or is characterized by materials associated with long-established or customary practices.
-
E.
standardEquipmentOrigin
Indicates that an item’s standard equipment comes from or is originally supplied by a specified source or origin.
- 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_69d807657e8c8190bd9435ee2f823845 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97ece22908190a0941e23df7c774d |
completed | April 10, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69d97dc39a0881908119c62e31bf6182 |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 8:51 p.m.