Triple
T36196566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Pumpkin |
E1047142
|
entity |
| Predicate | primaryBeliever |
P9182
|
FINISHED |
| Object | Linus van Pelt |
E324004
|
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: Linus van Pelt | Statement: [Great Pumpkin, primaryBeliever, Linus van Pelt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryBeliever Context triple: [Great Pumpkin, primaryBeliever, Linus van Pelt]
-
A.
originBelief
Indicates a belief or assumption about where something or someone comes from or originated.
-
B.
mainFaith
Indicates that one entity is the primary or predominant religious belief or faith tradition associated with another entity.
-
C.
primaryFaithfulConcentratedIn
Indicates that the primary or most significant loyal following or adherence to something is geographically or demographically concentrated in a particular place or group.
-
D.
hasCentralBelief
Indicates that a particular belief is a core or foundational belief within an entity’s overall belief system.
-
E.
believedBy
chosen
Indicates that a particular proposition, statement, or entity is held to be true or accepted as real by a specified believer.
- 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_69f76e414bdc8190996f15a544220a3d |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a393419746c8190a2f56199d956d8de |
completed | June 22, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:08 p.m.