Triple
T29163582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scire |
E739251
|
entity |
| Predicate | userNotableFor |
P4829
|
FINISHED |
| Object | founding modern Wicca |
—
|
LITERAL 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: founding modern Wicca | Statement: [Scire, userNotableFor, founding modern Wicca]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: userNotableFor Context triple: [Scire, userNotableFor, founding modern Wicca]
-
A.
notableUser
chosen
Indicates that the user holds a special or distinguished status, such as being recognized, influential, or otherwise noteworthy within a given context.
-
B.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
C.
subjectNotableFor
Indicates that the subject is especially recognized or distinguished for a particular attribute, achievement, role, or characteristic.
-
D.
holderNotableFor
Indicates that a holder (such as a person or organization) is particularly known or recognized for a specific role, achievement, work, or characteristic.
-
E.
notableActivityIn
Indicates that an entity is particularly recognized for performing a significant activity within a specified place, context, or domain.
- 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_69f07cb528fc8190a556b73990c347c8 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f662d421f88190ac5e65ae10e5c2b7 |
completed | May 2, 2026, 8:47 p.m. |
| PD | Predicate disambiguation | batch_69f65c24f8b48190af81b575f3c15be5 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 11:49 a.m.