Triple
T23049532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Louise Belcher |
E573968
|
entity |
| Predicate | notableAccessory |
P31021
|
FINISHED |
| Object | pink bunny ear hat |
—
|
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: pink bunny ear hat | Statement: [Louise Belcher, notableAccessory, pink bunny ear hat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableAccessory Context triple: [Louise Belcher, notableAccessory, pink bunny ear hat]
-
A.
accessory
chosen
Indicates that one entity serves as a supplementary or supporting item to another, often enhancing its function, use, or appearance.
-
B.
notableAsset
Indicates that an entity possesses or is associated with an asset that is particularly significant, prominent, or noteworthy in relation to it.
-
C.
notableRelic
Indicates that an entity is a historically or culturally significant relic associated with another entity (such as a place, person, or event).
-
D.
notableTie
Indicates a significant connection or association between entities that is noteworthy or distinguished in some context.
-
E.
notableOrnamental
Indicates that something is recognized as a particularly significant or distinguished example of ornamental decoration or design.
- 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_69e245b9c11481909d06c872214d21af |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1867b800881909fabf9dca994c9e7 |
completed | April 29, 2026, 4:18 a.m. |
| PD | Predicate disambiguation | batch_69ef89d5f71881908b9f9d0c8aab278c |
completed | April 27, 2026, 4:07 p.m. |
Created at: April 17, 2026, 3:54 p.m.