Triple
T20891035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | After Bathing at Baxter's |
E514405
|
entity |
| Predicate | hasNoncommercialStructure |
P24924
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [After Bathing at Baxter's, hasNoncommercialStructure, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNoncommercialStructure Context triple: [After Bathing at Baxter's, hasNoncommercialStructure, true]
-
A.
isNonCommercial
chosen
Indicates that the associated entity, use, or activity is not intended for or involved in commercial, profit-generating purposes.
-
B.
hasCommercialAppeal
Indicates that something possesses qualities likely to attract buyers or generate profitable market interest.
-
C.
hasCommercialFunction
Indicates that an entity serves a commercial role or purpose, such as engaging in trade, sales, or other profit-oriented activities.
-
D.
haveStructure
Indicates that an entity possesses a particular internal organization, arrangement, or structural composition.
-
E.
hasLegalStructure
Indicates that an entity possesses a specific formal legal organization or classification under law.
- 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_69e0b4f7ebe48190952a85547a0f31a1 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6d05e307081908f1d044e877017ec |
completed | April 21, 2026, 1:18 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a8dc148190b33ff51894e2a8f9 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:46 p.m.