Triple
T35881267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mystery Inc. |
E1037512
|
entity |
| Predicate | primaryInvestigator |
P86847
|
FINISHED |
| Object | Velma Dinkley |
E318071
|
NE 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: Velma Dinkley | Statement: [Mystery Inc., primaryInvestigator, Velma Dinkley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryInvestigator Context triple: [Mystery Inc., primaryInvestigator, Velma Dinkley]
-
A.
coPrincipalInvestigator
Indicates that an entity serves jointly with another as a principal investigator on the same research project or grant.
-
B.
principalInvestigatorCountry
Indicates the country with which the principal investigator is affiliated or based.
-
C.
chiefScientist
Indicates that one entity serves as the primary or lead scientist for another entity, typically holding top scientific authority or responsibility.
-
D.
primaryCollaborator
Indicates that one entity serves as the main or most significant partner working jointly with another entity on a shared activity, project, or goal.
-
E.
researchLedBy
chosen
Indicates that a research project, study, or investigation is directed or overseen by a specified leader or principal investigator.
- F. None of above.
Provenance (4 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_69f76e1f4d748190bb55594d8441d70e |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38b6ed37388190bbd6b8ed80a63f9b |
completed | June 22, 2026, 4:15 a.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:06 p.m.