Triple
T38577095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delray Affair |
E929434
|
entity |
| Predicate | approximateNumberOfArtistsAndCrafters |
P201560
|
FINISHED |
| Object | hundreds |
—
|
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: hundreds | Statement: [Delray Affair, approximateNumberOfArtistsAndCrafters, hundreds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateNumberOfArtistsAndCrafters Context triple: [Delray Affair, approximateNumberOfArtistsAndCrafters, hundreds]
-
A.
approximateNumberOfPerformers
Indicates an estimated count of performers involved in an event or performance.
-
B.
associatedCraftsmen
Indicates that there is a relationship linking an entity to one or more craftsmen who are connected to it through work, creation, or service.
-
C.
representedArtists
Indicates that one entity (typically an agent, gallery, or organization) serves as the professional representative for another entity (typically an artist) in managing or promoting their work.
-
D.
numberOfMusicians
Indicates the quantity of musicians associated with a given entity or event.
-
E.
employedCraftsmenFrom
Indicates that one entity has hired or utilizes craftsmen originating from another entity.
- 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_69f76ebd2248819083978362d81fa35e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a0004582bb08190b8d0b88251e8d333 |
completed | May 10, 2026, 4:06 a.m. |
| PD | Predicate disambiguation | batch_6a0003e3e5588190933beea5fb28f150 |
completed | May 10, 2026, 4:04 a.m. |
| PDg | Predicate description generation | batch_6a00045774ec81908ca607565b074f31 |
completed | May 10, 2026, 4:06 a.m. |
Created at: May 3, 2026, 4:32 p.m.