Triple
T21072382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arte dei Legnaioli e Mobilieri |
E519138
|
entity |
| Predicate | organizedWorkersIn |
P142735
|
FINISHED |
| Object | woodworking trades |
—
|
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: woodworking trades | Statement: [Arte dei Legnaioli e Mobilieri, organizedWorkersIn, woodworking trades]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: organizedWorkersIn Context triple: [Arte dei Legnaioli e Mobilieri, organizedWorkersIn, woodworking trades]
-
A.
organizedAt
Indicates that an event or activity was arranged, planned, or hosted at a specific location or venue.
-
B.
organizedAs
Indicates how elements are structured, arranged, or grouped according to a particular organizing principle or scheme.
-
C.
organizedDuring
Indicates that an event or activity was arranged or took place within a specified time period or temporal context.
-
D.
involvesWorkers
Indicates that an event, process, or situation includes workers as active participants or affected parties.
-
E.
organización
Indicates that an entity is an organization or participates in an organizational structure or grouping.
- 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_69e0b506e59c8190849b71ed07929215 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e702d342908190ab3f365d89641fd2 |
completed | April 21, 2026, 4:53 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf9d71881908cd85dfc37db93ca |
completed | April 20, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69e5e2e03d88819086f8b641656ad8b0 |
completed | April 20, 2026, 8:25 a.m. |
Created at: April 16, 2026, 2:46 p.m.