Triple
T33127148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Giacomo di Benincasa |
E847750
|
entity |
| Predicate | hasOccupationIndustry |
P62538
|
FINISHED |
| Object | wool trade |
—
|
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: wool trade | Statement: [Giacomo di Benincasa, hasOccupationIndustry, wool trade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOccupationIndustry Context triple: [Giacomo di Benincasa, hasOccupationIndustry, wool trade]
-
A.
hasOccupationSector
chosen
Indicates that an entity’s occupation belongs to or is categorized within a particular economic or professional sector.
-
B.
hasIndustryRole
Indicates that an entity holds or performs a specific role, function, or position within a particular industry or sector.
-
C.
occupationType
Indicates the specific kind or category of work, profession, or role that an entity performs or holds.
-
D.
occupantIndustry
Indicates the industry or sector in which an occupant (such as a tenant or user of a space) operates.
-
E.
hasOccupationInWork
Indicates that an entity holds or performs a specific occupation within a particular work, project, or creative production.
- 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_69f349588f088190b7c9588860f72033 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d7205a588190af68e11ec875402d |
completed | May 3, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_69f6d27224708190b31a541cebe0ff77 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:27 a.m.