Triple
T27921057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Millbrook psychedelic community |
E706202
|
entity |
| Predicate | hadCoreMember |
P20032
|
FINISHED |
| Object | Richard Alpert |
—
|
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: Richard Alpert | Statement: [Millbrook psychedelic community, hadCoreMember, Richard Alpert]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadCoreMember Context triple: [Millbrook psychedelic community, hadCoreMember, Richard Alpert]
-
A.
hasCoreMember
chosen
Indicates that an entity includes another entity as a central or primary member of its group, organization, or structure.
-
B.
hadMember
Indicates that an entity was formerly a member or part of another entity or group.
-
C.
hadMembershipType
Indicates that an entity possessed or was assigned a specific type or category of membership.
-
D.
hasAssociateMember
Indicates that an entity has another entity connected to it in a non-full, typically limited or secondary, membership capacity.
-
E.
hasMembershipBy
Indicates that an entity holds or acquires membership in a group, organization, or program by means of a specified agent, process, or instrument.
- 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_69ef96b6cc808190aab19fb18b235f4b |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 27, 2026, 6:57 p.m.