Triple
T33093487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slinky |
E846845
|
entity |
| Predicate | wasCoDevelopedBy |
P6901
|
FINISHED |
| Object | Betty James |
—
|
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: Betty James | Statement: [Slinky, wasCoDevelopedBy, Betty James]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasCoDevelopedBy Context triple: [Slinky, wasCoDevelopedBy, Betty James]
-
A.
alsoDevelopedIn
Indicates that something was additionally developed in another context, location, or environment beyond the primary one already specified.
-
B.
isDevelopedBy
Indicates that something (such as a product, project, or idea) is created, produced, or brought into existence through the work or effort of a particular developer or group of developers.
-
C.
coDeveloperOf
chosen
Indicates that two or more entities jointly developed or collaborated in creating the same project, product, or work.
-
D.
formerlyDevelopedBy
Indicates that an entity was developed in the past by another entity, but is no longer developed by that same party.
-
E.
wasDevelopedIn
Indicates that an entity (such as a product, technology, or work) came into existence or was created during a specific time period or at a particular place.
- 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_69f3495590dc8190aa04f3dec74ce976 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:26 a.m.