Triple
T27781929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Camp Nowhere |
E699353
|
entity |
| Predicate | hasAdultAccompliceCharacter |
P64043
|
FINISHED |
| Object | Dennis Van Welker |
—
|
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: Dennis Van Welker | Statement: [Camp Nowhere, hasAdultAccompliceCharacter, Dennis Van Welker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdultAccompliceCharacter Context triple: [Camp Nowhere, hasAdultAccompliceCharacter, Dennis Van Welker]
-
A.
accompliceAge
Indicates that one entity’s age is the age of a person who acted as an accomplice in relation to another entity or event.
-
B.
isAdultCharacter
chosen
Indicates that a character has reached adulthood, typically meeting the age or maturity criteria defining an adult within the given context.
-
C.
hasEnforcerCharacter
Indicates that an entity includes or is associated with a character who acts as an enforcer, carrying out enforcement or coercive roles on its behalf.
-
D.
hasGuardianCharacter
Indicates that one entity serves as a guardian or protective character for another entity.
-
E.
hasThiefCharacter
Indicates that an entity includes or features a character whose role or identity is that of a thief.
- 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_69ef6a4b5a9081909c9111396c2be3d2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 27, 2026, 5:10 p.m.