Triple
T38276453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Camelot (2023 revival) |
E1021969
|
entity |
| Predicate | hairAndWigDesignBy |
P50540
|
FINISHED |
| Object | Cookie Jordan |
—
|
NE NERFINISHED |
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: Cookie Jordan | Statement: [Camelot (2023 revival), hairAndWigDesignBy, Cookie Jordan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hairAndWigDesignBy Context triple: [Camelot (2023 revival), hairAndWigDesignBy, Cookie Jordan]
-
A.
hairCraftedBy
chosen
Indicates that a hairstyle or hair-related work was created or styled by a specific person or agent.
-
B.
hairSpecialty
Indicates a professional focus or expertise in working with a particular type, style, or treatment of hair.
-
C.
hairdressingClientele
Indicates that one entity serves as the customer or client receiving hairdressing services from another entity.
-
D.
servesHairConcern
Indicates that a product, service, or action addresses or is intended to treat a specific hair-related concern.
-
E.
hairDetail
Indicates a relationship that specifies particular characteristics or attributes of an entity’s hair, such as style, color, length, or texture.
- 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_69f76df0cddc81908d16c1556ff4097f |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:30 p.m.