Triple
T26171107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LessWrong |
E654402
|
entity |
| Predicate | communityInfluence |
P65945
|
FINISHED |
| Object | effective altruism community |
—
|
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: effective altruism community | Statement: [LessWrong, communityInfluence, effective altruism community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: communityInfluence Context triple: [LessWrong, communityInfluence, effective altruism community]
-
A.
influencesCommunity
chosen
Indicates that one entity has an effect on the behavior, attitudes, or conditions of a community.
-
B.
communityAspect
Indicates that something pertains to, reflects, or influences the communal or social dimension of a group or community.
-
C.
hasSocialInfluenceThrough
Indicates that one entity exerts social influence on another specifically by means of an intermediary channel, platform, or relationship.
-
D.
communityType
Indicates the classification or category of community to which an entity belongs (e.g., urban, rural, online, professional).
-
E.
communityUsage
Indicates how something is used, adopted, or engaged with by a particular community or group of people.
- 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_69ee5b44391c81908bdbd8813ba9aa99 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6456608190b94e7c2e2c2a4824 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 26, 2026, 8:35 p.m.