Triple
T25944668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little Darlings |
E653805
|
entity |
| Predicate | hasCampSettingType |
P10334
|
FINISHED |
| Object | girls' summer camp |
—
|
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: girls' summer camp | Statement: [Little Darlings, hasCampSettingType, girls' summer camp]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCampSettingType Context triple: [Little Darlings, hasCampSettingType, girls' summer camp]
-
A.
hasCampType
chosen
Indicates that an entity is associated with or classified by a particular type or category of camp.
-
B.
hasSetting
Indicates that an entity takes place, occurs, or exists within a particular environment, context, or location.
-
C.
hasSettingBy
Indicates that something (such as a work, event, or scenario) has its contextual environment, location, or background defined or established by a particular agent or source.
-
D.
hasUserSetting
Indicates that a user is associated with a specific configuration or preference setting.
-
E.
hasSettingRole
Indicates that an entity participates in a setting by fulfilling a specific contextual or functional role within it.
- 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_69e7ab3fd2f881908837305e4ba98011 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 22, 2026, 8:41 a.m.