Triple
T35187550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calvin |
E1016029
|
entity |
| Predicate | fullFormOfFoundedGroup |
P163685
|
FINISHED |
| Object | Get Rid Of Slimy girlS |
—
|
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: Get Rid Of Slimy girlS | Statement: [Calvin, fullFormOfFoundedGroup, Get Rid Of Slimy girlS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fullFormOfFoundedGroup Context triple: [Calvin, fullFormOfFoundedGroup, Get Rid Of Slimy girlS]
-
A.
foundingMembersCollectiveName
Indicates the shared collective name used to refer to the group of founding members.
-
B.
foundedAsGrouping
Indicates that an entity was originally established or created as part of a particular group, category, or organizational grouping.
-
C.
organizationFoundedAs
chosen
Indicates that an organization was originally established under a particular name, form, or predecessor entity.
-
D.
movementFoundedInYear
Indicates the specific calendar year in which a movement was established or came into existence.
-
E.
organizationFounded
Indicates that an organization was established or created at a specific point in time, often by a particular founder or founding entity.
- 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_69f76ddd815c8190b822eea06630f9fb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78dc3776c8190bbd4702acd5a191e |
completed | May 3, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69f78b9106008190930b3b3675b737d6 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:02 p.m.