Triple
T23049533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Louise Belcher |
E573968
|
entity |
| Predicate | neverSeenWithout |
P150786
|
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, neverSeenWithout, pink bunny ear hat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: neverSeenWithout Context triple: [Louise Belcher, neverSeenWithout, pink bunny ear hat]
-
A.
neverRepresentedBy
Indicates that one entity has at no time been represented or acted on behalf of by the other entity.
-
B.
neverCaptured
Indicates that the subject has not at any time been apprehended, seized, or taken into custody by another entity.
-
C.
notObservedIn
Indicates that a particular entity, event, or property has not been detected, recorded, or seen within a specified context, dataset, or environment.
-
D.
notObservedOn
Indicates that a particular entity, event, or condition was explicitly not observed or recorded at a specified time or context.
-
E.
neverPerformed
Indicates that the specified action or event has not occurred at any time for the given entity or between the given entities.
- 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_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. |
| PDg | Predicate description generation | batch_69ef9b7494f4819088ae59ea3d0ae8ab |
completed | April 27, 2026, 5:23 p.m. |
Created at: April 17, 2026, 3:54 p.m.