Triple
T34728096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glen Schofield |
E1001125
|
entity |
| Predicate | foundedForProject |
P121179
|
FINISHED |
| Object | The Callisto Protocol |
—
|
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: The Callisto Protocol | Statement: [Glen Schofield, foundedForProject, The Callisto Protocol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedForProject Context triple: [Glen Schofield, foundedForProject, The Callisto Protocol]
-
A.
foundedProject
chosen
Indicates that an entity initiated and established a particular project.
-
B.
foundedFor
Indicates that an entity was established or created specifically to serve, support, or benefit another entity or purpose.
-
C.
providedFoundationFor
Indicates that one entity served as the essential basis, support, or groundwork enabling the existence, development, or success of another entity or outcome.
-
D.
fundedProject
Indicates that a funding entity has provided financial support to a specific project.
-
E.
foundedWith
Indicates that an entity was established or created together with another entity, typically as co-founders or jointly initiated partners.
- 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_69f76daeb6e48190a4c9a6b0edc80f72 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fed83b1d188190a318b0ad3003200a |
completed | May 9, 2026, 6:46 a.m. |
| PD | Predicate disambiguation | batch_69fed78e03548190b6e6ad93ae8d131d |
completed | May 9, 2026, 6:43 a.m. |
Created at: May 3, 2026, 3:59 p.m.